A rather geeky/technical weblog, est. 2001, by Bramus
If you have a public repository with a Dockerfile you can have users automatically deploy the container to Google Cloud Run by adding a Cloud Run Button. It’s no more than an image that links to https://deploy.cloud.run, like so: [](https://deploy.cloud.run) Add that code to your README.md and when a visitor follows that …
Deploying one site (from a single source repo) to Netlify ain’t that hard – see my instructions here – but what if your sources are spread out across multiple repos? How do you combine the data without duplicating it into a monorepo? That’s exactly the problem Spatie was having for their docs.spatie.be: the website holds …
fastlane are an awesome bunch of tools. Josh Holtz has recently started Fastlane Screencast, a website with videos/tutorials for explaining and implementing built-in fastlane tools, fastlane actions, third-party fastlane plugins, continuous integration, and anything else that fastlane can possibly do. The first video covers integrating fastlane into your Ionic Framework build process: A second tutorial …
Continue reading “Fastlane Screencast: Integrate fastlane into your Ionic Framework build process”
Δnow allows you to take your JavaScript (Node.js) or Docker powered websites, applications and services to the cloud with ease, speed and reliability. Every time you deploy a project, Δnow gives you a unique URL to it (even before build processes are complete!). When it’s time to take your deployment to production, you simply pick …
All deployments happen in chat via Hubot commands, which ensures that everyone in the company (from development to operations to support) has visibility into changes that are being pushed into production. Deploying branches to GitHub.com → Reminds me of how deployments at Etsy happen. They’ve got Deployinator integrated into IRC and deploy using deployment trains. …
// Contents of Envoy.blade.php @servers(['web' => 'deploy-ex']) <?php $repo = '[email protected]:Servers-for-Hackers/deploy-ex.git'; $release_dir = '/var/www/releases'; $app_dir = '/var/www/app'; $release = 'release_' . date('YmdHis'); ?> @macro('deploy', ['on' => 'web']) fetch_repo run_composer update_permissions update_symlinks @endmacro @task('fetch_repo') [ -d {{ $release_dir }} ] || mkdir {{ $release_dir }}; cd {{ $release_dir }}; git clone {{ $repo }} {{ $release …
; This is a sample deploy.ini file. ; You can specify as many servers as you need ; and use whichever configuration way you like. [staging] user = example pass = password host = staging-example.com path = /path/to/installation port = 21 passive = true [production] user = example pass = password host = production-example.com path …
On a recent project I collaborated on, deployment happened via git-ftp.py, a Python script which automatically publishes your git repository to an FTP server. The script itself works with with an git-rev.txt file on the FTP server which keeps track of the last published commit. When deploying via git-ftp.py, the script only uploads the changes …
Continue reading “Automatic Website Publishing with git-ftp.py on Mac OS X”