- This topic is empty.
-
Posts
-
HI All,
I figure the best way to get started with a new software project is with an install question. To be clear I’ve used Bizuno for the last ~9 years or so, both hosted and on my “own” servers (vps in a data center). Over the last day or so I have gone over the various install methods. I am sort of intrigued by the Docker option, but I also have a standard VPS waiting for something to do which could be a LAMP/Linux install, and I have ISPconfig also already setup with plenty of room for a Bizuno install. So I am weighing my options trying to make the best next move. In the ISPconfig dept, I get flexibility to add another site, project, web shop etc to the same server without too much difficulty, and things like SSL, setup etc. are all things I have done before. With the regular VPS install, adding a second site etc. would be a learning experience for me, but hey cheap VPS’s are cheap, I could just rent another if I need to. But both of these options are out on the internet, with my data and lively hood sort of sitting there waiting for someone to find the crack in the wall that I missed. I have successfully set up and used options like both of these before. Docker on the other hand promises both an easy install and something more setup to run on our inhouse server behind our firewall with 99.9% of the bad stuff kept out on the other side. I have never run Bizuno in this environment, I suspect it will be faster and being inside the firewall, more secure with less effort. The questions that come to mind are will things that require communication outside the firewall work? I suspect email, credit card charges and UPS/Fedex labels all initiated inside, should reach out and function well/easily. That said, I am not actually sure of that. Also we would be looking at setting up a web shop that would integrate with bizuno, would something like that be able to connect and manually sync? Like we could run it a couple times a day? EDI?, it is many steps down the list, but something I am keeping open as an option. And then the last docker question is, I get the feeling maybe it’s not ready for production? More for evaluation. Is it evaluation because it’s easy? Or evaluation because there is some reason it shouldn’t be used for production? I’m looking to choose the right path to go down because I know it will likely take a good amount of time and I don’t want to “try” multiple incorrect paths. Any guidance or insight into these paths before me would be greatly appreciated.
Thanks,
BCbrett
- You must be logged in to reply to this topic.