@Harper
Can you elaborate on what you mean by automating the deployment process?
Casey said:
@Harper
Can you elaborate on what you mean by automating the deployment process?
Previously, after building a website, I’d create a new cPanel account through the shared hosting WHM. After account creation, I’d log in to set up the website database, create the user, assign permissions, upload the database, and manually upload website directories. Purchasing an SSL certificate (through Namecheap) and getting it in place was last on my list.
This process was tedious and manual. A few weeks ago, I began automating this with Docker. We created reusable templates and bash scripts for future website and web application work. Now, we commit code to our repository, and Bitbucket pipelines execute the rest—copying files to the server, building and rebuilding the database, and handling SSL certificates automatically. We only need to define preset environment variables like server IP, ssh private key, etc. Setting up the hosting server takes minutes, especially with Digital Ocean’s API.
It took considerable effort upfront, but it has been a game changer. Should have done this earlier!
@Harper
Thanks for elaborating. This is definitely something I want to explore at some point. I’m freelance, and while I’m currently not overwhelmed, renewing SSL for my growing client base is getting tedious.
@Casey
No problem! I felt the same way until I became busy, and it became clear how inefficient the process was.
64GB waterproof flash drive at the bottom of the ocean.
Depending on client requirements: DigitalOcean, GCP, AWS, Hetzner, self-hosting (if they prefer managing it themselves).
They are not my websites; they’re my clients’ websites, so they choose.
If they don’t have a preference, I suggest a provider (mostly Hetzner) and ask them to create an account, fill in billing details, and add me to their team. We do this alongside a video call if they aren’t tech-savvy.
I also suggest using Cloudflare for the CDN and request access to manage their account. If needed, I buy the domain there.
I host my websites on my server. My client gets a fully functional website and not one installed on someone else’s server. Not a popular perspective, I guess.
I have a SiteGround shared hosting account for small sites; for larger, busier sites, I use a mixture of Digital Ocean and Hetzner VPSs. I’m in the process of switching from ServerPilot to RunCloud for server management, so it’s currently a mixture of both.
Jordan said:
@Zion
Nope, because Pressable is owned by Automattic.
Oh, of course! I didn’t realize that was their competing product.
I moved over a decade ago. Friendlier staff and a smoother system. Highly recommended.
If it’s WordPress, I use pressable.com.
For everything else, usually Firebase since clients don’t expect to access the backend (for web apps and database-driven projects).
Jaden said:
If it’s WordPress, I use pressable.com.
For everything else, usually Firebase since clients don’t expect to access the backend (for web apps and database-driven projects).
I guess I need to move on from WPEngine. But are they going to get sued for having ‘Press’ in their name?
Jordan said:
@Zion
Nope, because Pressable is owned by Automattic.
Oh, of course! I didn’t realize that was their competing product.
Hey, I need to hire help. I’m being messed with in the most uncool ways and need to find someone to pay for developer help. I used to work with old devices, but now I can’t even chat on FB or send emails, no matter how many new devices I try.
It depends on the site. We use various hosting solutions in our small agency—Netlify, Cloudflare pages, dedicated servers or VPS. The choice depends on the site and its underlying technology.
Laravel Forge for managing servers and projects (not just for Laravel; I use it for all projects—WordPress, Nuxt, SvelteKit, Next, custom). Servers are usually on Hetzner or Digital Ocean. Even though Forge is a paid service, it saves me a lot of time.
A cluster of old computers in a basement connected to a bi-directional 1 GB fiber line. This wasn’t too bad when I had a few high-end clients, but I’m considering moving to the cloud soon because I want to leave Canada and travel.
Digital Ocean + Laravel Forge. It’s cheap, easy to set up, and all my projects are built in Laravel.
I build WordPress sites for clients. I host my own site on Cloudways. For small clients with low traffic, I host them on my account and bill them. For those with medium to high traffic, I refer them to SiteGround, using my affiliate link, which gives me a $50 referral fee. I gain collaborator access to manage their SiteGround account.
I use both Netlify and VPS.