Has anyone thought through the DevOps workflow here? The best thing I’m coming up with is creating an account for every environment. Is that allowed though? Seems like, for any serious project, it would take up all three accounts. Development, user acceptance testing, then production. Is it possible to sign up multiple times? Or is there another way to do this? I usually have something like https://domain.com, https://dev.domain.com, and https://uat.domain.com. Doesn’t seem like that is reasonable here though.
It’s against the rules.
Do note that you can not split subdomains from the same base domain into different accounts. Even if you want to take up three accounts, it’s not possible to do it like this
7 Likes
Alright, one account, separate domains for different environments. I’m curious though. If someone were to say, “Hey, can you build me a website? I don’t have much money.”, and I was like, “InfinityFree might be a good option.”, could I create them an account, or have them create an account and login, or check in the code to DevOps and have it be deployed?
No, it’s against the rules.
This might be OK, but you probably want to wait for Admin for a more definite answer.
Automatic deployments are OK, but do note that there’s only FTP. Using other tools such as git is simply not supported.
6 Likes
Alright, I’m not sure if anyone cares, but I setup DevOps. I do development on the development environment, get everything working, copy the files locally via script, perform a Git commit, push the files, then run a pipeline for production deployment. I made the project public in case anyone would like an example:
Deployment pipeline YAML is here:
Repository is here:
Do you even need separate development and acceptance environments in the first place? It’s perfectly reasonable to not have them if your release process doesn’t need them. Especially nowadays, the cool kids strive for fast iteration and frequent releases, which can all very achievable with modern tools for automated testing and deployments. Building out a full DTAP pipeline is not necessary to be able to do high quality releases.
If I were you, I would much rather setup a good local dev environment instead of having to work on a remote server. Building an exact replica of our environment is not feasible, but it’s much easier if you can do most of your development locally without having to copy files between your computer and a remote server.
I’m well aware that DevOps is a very bloated term which can mean wildly different things to different people. And this is largely unrelated to your question, but calling a DTAP pipeline a “DevOps workflow” seems very far from any definition I know.
DevOps mostly has to do with how dev and ops teams work together. The thing with web hosting is that there is very little ops work in the first place: managing the servers and production environment is done by us. The whole idea is that you can just do the dev and completely outsource the ops to us.
Unless DevOps to you means “how do developers throw their code over the fence to the ops team to deploy and maintain it”, then your question has little do with DevOps. And if that’s your definition, then you’re doing the entire thing that DevOps wants to remove. The whole point of DevOps is to remove this fence that code is being thrown over.
5 Likes
Right now I’m only concerned with development and production. But given any business
users, I think UAT would become necessary. Development is unstable. Change this, change that, bring the entire site down, fidget, fidget, ah, okay, I think it’s working. Deploy. Then, beyond proof of concept, it needs some sort of verification. If that’s alpha/beta users, the business, whatever, but someone to say, this checks out. Then production of course, the stable environment when sign-off is obtained. I don’t understand how something could be run with any lesser resources. Given a more rigorous process, you of course have quality assurance, but then, I think that would grow beyond the free offering. So it seems like, given the rules, InfinityFree is saying focus on one project if you’re serious about using our services. I can get with that.
I was thinking a bit more about this. It seems like you are saying, “Setup a good local development environment.”, then, “Hey, let us manage all of the environments, that’s what we’re good at, and that’s what we’re here for.” Doesn’t make sense to me. It makes sense to have like environments to me.
you can create an unlimited number of subdomains on one user account, each of which has its own document root and runs as its own site.
3 Likes
Normally, you’d want to have a local development environment that resembles production as closely as possible.
You want it to be local because it’s much easier just working on code on your own computer without having to upload it to external servers. It also scales if you have multiple developers working on the same code.
I do acknowledge that the resembling production part is quite difficult with web hosting, because you’re always dealing with the web hosting provider’s server setup and configuration which is very likely different from your own. But in my personal opinion, I would still much rather develop locally with a “close enough” production-like environment and deal with bugs down the line rather than forego local development entirely and always work on a remote FTP server.
5 Likes
I’m not sure. The trend of container orchestration seems to be empirical practice saying otherwise. Unless you are producing images as well?
@AnthonyBrianMallgren , change your password for the hosting account if0_39062711 in the dashboard, you leaked the password in the files you shared. You will not be able to access your files or databases until you do so.
This is why you don’t randomly post code publicly.
Also, putting passwords in plaintext in your code file is a very bad idea. Especially if you plan to send that code through various platforms, and especially if you plan to share that code online.
7 Likes
Also, this is not true. There is a limit on the number of subdomains you can have (I believe the limit is 50), but if you are registering them and not using them, your account can be suspended for hogging resources.
6 Likes
If you look at the YAML, there is a process to replace values in the configuration file from secure DevOps variables. Not totally sure, but if hosting was setup to make version control easier, I don’t believe this would have happened.
I’ve updated the password and pulled the file from the old development environment. Please don’t guide people away from proper process.
I’m not sure what you mean by proper process …
- Posting passwords online is not proper process
- Pasting passwords in plaintext within a codefile is not proper process
- Hardcoding sensitive information into an application is not proper process
Also, don’t go blaming your mistake on the host. It is not a 3rd party’s fault that you broke standard practice and did not check your work.
6 Likes
Maybe, maybe not. But end of the day the free hosting is aimed primarily at individuals wanting to host a site. Not professionals/semi-profesionals looking for a full dev-ops environment
5 Likes
The general messaging I get is we don’t want quality people in information technology. Got the message loud and clear.
1 Like
That’s not the case at all. But you have to realise that with a free service you won’t get the same tools and facilities as a paid service.
If you want a full Dev ops environment that’s going to cost
5 Likes
Infinity free is run by 1 individual (admin) who’s only income from the site is ad revenue and referrals to iFastNet. Hardly a 6 figure salary.
I understand you’re frustration. I’m a dev now with my employer, where we use one of the worlds biggest CMS systems. And use dev, UAT and prod environments. Id love to do that with my own sites. But that kind of infrastructure costs significantly more than what’s available through here.
End of the day you have to be realistic. A free service has limitations. This is one of the limits. Noone is forcing you to use infinity free, so no carrot and stick strategies
8 Likes