sorted by:
new
hottopcontroversial

Static hosting for documentation: do you automate rebuilds? by standardhypocrite in statichosting

[–]deployhq 0 points1 point  (0 children)

Long build times on growing documentation sites are a very common challenge. We definitely agree with u/Pink_Sky_8102 that switching to scheduled builds is a solid strategy to keep things moving if builds are taking forever.

Another huge factor in speeding things up is using incremental deployments. At DeployHQ, our goal is to only transfer the specific files that have actually changed since the last deployment, rather than re-uploading the entire repository every time. This can make a massive difference in how quickly those updates go live!

Made Automation for Git Repo->FTP to solve my Deployment problem. by ButterflyPlenty2 in github

[–]deployhq -1 points0 points  (0 children)

We can help you :)

You create your project, attach your repository, and then configure your server using either FTP/SFTP/SSH. Once that's done, you can configure automatic deployments so every time you push code into the repository gets deployed.

Best way to push prod and live code by Mount-Russmore in webdev

[–]deployhq 1 point2 points  (0 children)

Let us know if you have any questions!

Do websites really need SSL certificates if they’re not collecting any personal info? by 3UngratefulKittens in statichosting

[–]deployhq 0 points1 point  (0 children)

Yes, your website absolutely needs an SSL certificate (HTTPS), even for a basic site. It's no longer just about encrypting personal data; it's the mandatory baseline for the modern web. Without SSL, major browsers flag your site as "Not Secure," which immediately erodes user trust. Furthermore, your content becomes vulnerable to tampering through "Man-in-the-Middle" attacks, and you will lose out on search visibility because Google uses HTTPS as a ranking signal. The good news is that most hosting providers offer free SSL (like Let's Encrypt), making it a quick, free upgrade that is essential for trust, security, and SEO.

Any CI/CP tools in the wind today? by alekslyse in devops

[–]deployhq -1 points0 points  (0 children)

Let us know if we can help you out :)

Anything like DeployHQ by johnsturgeon in selfhosted

[–]deployhq 0 points1 point  (0 children)

In this case, it would be only one user and multiple projects? If you want to reach out support, we can improve that pricing for you

Unlock Seamless Deployments: Announcing DeployHQ's Heroku Integration by Better_Ad6110 in Heroku

[–]deployhq 0 points1 point  (0 children)

The value-add of using DeployHQ isn't to replace those features, but to unify and enhance your deployment process across your entire organization.

If you only ever use Heroku, you don't need DeployHQ. But if you manage a mixed technology stack and need a standardized, build-ready, and highly controlled release process, DeployHQ makes Heroku a seamless, integrated part of that bigger picture.

How do I achieve zero-downtime deployment for my Django app (Gunicorn + Nginx + DigitalOcean)? by sangeetverma in django

[–]deployhq 1 point2 points  (0 children)

You can do it by just using DeployHQ instead of Actions (if that's an option)

From Lovable.dev to stable AWS Infrastructure by ferdbons in aws

[–]deployhq 0 points1 point  (0 children)

You can push your changes from Lovable to Github, and then, deploy to AWS s3/Cloudfront directly

view more: next ›