Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How to set up continuous deployment using free hosted tools

simonwillison.net

Post reply on HN
Print view View original

61–70 of 92 posts

Re: How to set up continuous deployment using free hosted tools

#61

Post by james-skemp »

planetjones wrote: post #52

Not sure bitbucket pipelines are mentioned here. But for free I manage to commit Hugo source files to a private git repository, generate the static files by spinning up a docker container and generating them using Hugo and finally rsyncing the static output to my Webserver. All for free. You only get 50 minutes of time now (for free) in the docker instance but for simple continuous deployment cases like mine it’s ver…

You might want to look at Gitlab if you want to drop the need for a web server. Their pages support supports Hugo much better than GitHub (which leans toward Jekyll), and is pretty well documented.

Re: How to set up continuous deployment using free hosted tools

#62

Post by acejam »

jfaucett wrote: post #57

I can't believe the author doesn't mention gitlab. Setting up full CI on gitlab is amazing. They have the easily integratable gitlab runners i.e. travis-ci functionality + different build stages for automatic deployment via ansible/chef/whatever and unlimited free private projects to boot. If you're working on anything that can't be public I highly recommend gitlab. Its an amazing service. FYI: I am in no way affilia…

GitLab is great and has come a very long way over the last several years. However, I still gladly pay GitHub $7 a month for my private repos because I feel that GitHub truly does offer a better code review and repository experience. GitLab in certain places is still very rough around the edges, not to mention performance has always been a concern.

To me, GitHub still is the gold standard and will likely be for quite some time.

Re: How to set up continuous deployment using free hosted tools

#63

Post by acejam »

planetjones wrote: post #52

Not sure bitbucket pipelines are mentioned here. But for free I manage to commit Hugo source files to a private git repository, generate the static files by spinning up a docker container and generating them using Hugo and finally rsyncing the static output to my Webserver. All for free. You only get 50 minutes of time now (for free) in the docker instance but for simple continuous deployment cases like mine it’s ver…

The last time I tried using pipelines, it wouldn't let me use any arbitrary Docker image, I had to use one of the Atlassian "blessed" images. :/

Re: How to set up continuous deployment using free hosted tools

#64

Post by desireco42 »

planetjones wrote: post #52

Not sure bitbucket pipelines are mentioned here. But for free I manage to commit Hugo source files to a private git repository, generate the static files by spinning up a docker container and generating them using Hugo and finally rsyncing the static output to my Webserver. All for free. You only get 50 minutes of time now (for free) in the docker instance but for simple continuous deployment cases like mine it’s ver…

Add Netlify and it will continue to be free. I use Hugo as well, Netlify compiles Hugo on it's own, so I don't need workflows, but it is cool to have them.

Re: How to set up continuous deployment using free hosted tools

#66

Post by mopierotti »

nicodjimenez wrote: post #55
NightMKoder wrote: post #45

Once you need something a bit more heavyweight than Travis (e.g. more CPU) I would highly suggest Buildkite ( https://www.buildkite.com ). It’s a “bring your own machines” solution, which means you can have beefy machines (e.g. via buildkite on EC2 spot autoscaling), or even machines that run inside production without handing buildkite itself any secrets. We’ve been using it at Ladder and it’s been phenomenal. Also i…

+1 for mentioning Buildkite, also works great for machine learning

Is there a particular feature that's suited to machine learning? I'm having trouble understanding the connection.

Re: How to set up continuous deployment using free hosted tools

#68

Post by acejam »

IgorPartola wrote: post #38

Does anyone have a solution for a situation where I have a Django backend and a VueJS front end and want to run the Vue build step before deploying? Currently doing this with Git hooks and committing the resultant build, but that is bad for a number of reasons. This is running on Heroku. Would their release phase allow for this without significantly slowing things down? Would it deal with npm installs?

I've done this for several apps. We have a large Jenkins 2 cluster and use declarative Jenkinsfile's. For Jenkins, you can accomplish this by simply setting up a Jenkinsfile that has an agent defined in each stage. Build your VueJS app in the first stage with a NodeJS container, and build the second stage with a Python container. Bonus points for building an actual Docker image as your artifact that has Django inside of it with Apache or nginx serving the VueJS bits too.

Re: How to set up continuous deployment using free hosted tools

#69

Post by Domenic_S »

planetjones wrote: post #52

Not sure bitbucket pipelines are mentioned here. But for free I manage to commit Hugo source files to a private git repository, generate the static files by spinning up a docker container and generating them using Hugo and finally rsyncing the static output to my Webserver. All for free. You only get 50 minutes of time now (for free) in the docker instance but for simple continuous deployment cases like mine it’s ver…

Why is that better than generating static locally? Seems like a lot of fiddling for no benefit.

Re: How to set up continuous deployment using free hosted tools

#70

Post by y4mi »

james-skemp wrote: post #59
jfaucett wrote: post #57

I can't believe the author doesn't mention gitlab. Setting up full CI on gitlab is amazing. They have the easily integratable gitlab runners i.e. travis-ci functionality + different build stages for automatic deployment via ansible/chef/whatever and unlimited free private projects to boot. If you're working on anything that can't be public I highly recommend gitlab. Its an amazing service. FYI: I am in no way affilia…

I think I saw that GitHub now supports non-gh_pages branches, but Gitlab pages are also much easier to setup. I've moved all my sites to Gitlab pages generated via Hugo or Jekyll. Uptime (via Uptime Robot) just doesn't seem as good as GitHub, but it's not bad.

> , but Gitlab pages are also much easier to setup

uuh, what?

i think gitlab pages are wonderful, because you're not restricted to jekyll, but how is it easier to setup? you only need to toggle the checkpoint in the repository settings...

Post reply on HN