sudo apt install -y \
autoconf automake autopoint bash bison \
build-essential bzip2 flex g++ g++-multilib \
gettext git gperf intltool libffi-dev \
libgdk-pixbuf-2.0-dev libltdl-dev libssl-dev \
libtool-bin lzip make p7zip-full patch \
perl python3 python3-mako python3-pkg-resources \
ruby sed unzip wget xz-utils cmake ninja-build git wget
| #!/usr/bin/env php | |
| <?php | |
| function main(): int | |
| { | |
| try { | |
| // do stuff | |
| } | |
| catch (\Throwable $exception) { | |
| echo $exception->getMessage() . PHP_EOL; |
| <!-- 100 flocons pour un effet dense --> | |
| <div class="snowflake"></div> | |
| <div class="snowflake"></div> | |
| <div class="snowflake"></div> | |
| <div class="snowflake"></div> | |
| <div class="snowflake"></div> | |
| <div class="snowflake"></div> | |
| <div class="snowflake"></div> | |
| <div class="snowflake"></div> |
| version: '3' # Specify the Docker Compose version | |
| services: | |
| adguardhome: # Define the service named 'adguardhome' | |
| image: adguard/adguardhome # Use the 'adguard/adguardhome' Docker image | |
| container_name: adguardhome # Set the container name to 'adguardhome' | |
| restart: unless-stopped # Restart the container automatically unless stopped manually | |
| ports: # Map container ports to host ports | |
| # Expose port 53 on TCP and UDP for DNS queries | |
| - "53:53/tcp" |
Using repositories type path in monorepository, allows to require a composer vendor as a symlink from directory path.
When you run composer i this create a symlink in vendor/abenevaut/php-sdk from ../php-sdk.
Like this, you are able to dev your main project and the vendor at the same time.
Once you are ready to push the project to production, you don't want the symlink anymore and use the latest content of php-sdk vendor.
You can specify COMPOSER_MIRROR_PATH_REPOS=1 to copy directories and files, like normal way to use composer package, from php-sdk.
/!\ You have to deploy from a pipeline who have clone the whole monorepository base code.
Github Actions are defined in a YAML file named <workflow name>.yml and are listed in the .github/workflows folder at the root of your project.
You can store as many workflows as your project requires.
docker run --rm -it -w /app -v .:/app alpine/openssl genrsa -des3 -out rootCA.key 4096
docker run --rm -it -w /app -v .:/app alpine/openssl req -x509 -new -nodes -key rootCA.key -sha256 -days 1024 -out rootCA.crt- save passpharse and rootCA.key & rootCA.crt in a vault
- add root certificate
rootCA.crtin your OS (mac: https://www.eduhk.hk/ocio/content/faq-how-add-root-certificate-mac-os-x // windows: https://www.youtube.com/watch?v=Ddsrk68TGI0)
Initially, a business is like any other. It comes from the phenomenon of "start-up" or a matured idea. It seeks its place Upsets concurrency when there are and often starts as a bomb under the impulse of joy and novelty. Strong competition and lower prices for the hardware development allows companies who wish to conquer new market to equip in material quickly and easily. It was the same for the workforce. Number of students passionate ready to sweat water and blood to prove their capabilities and their mastery of the virtual world.
But it goes without saying that only the well-organized business and master of their efforts experiencing stable growth. To do this, in the context of an IT project, it is essential to establish a quasi-industrial system. This saves time and not losing (Hoo My F****** God I Used "rm *" ! [I know you know]).
Of course, this tutorial "Tips & Tricks" is just one example but it can proves useful in the context of a single project website. Then let your instincts do the rest ;-)
Wel