Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 3 years ago.
Improve this question
I'm trying to set up something similar to Docker for deploying a spring application in Solaris. I thought of Solaris zones but it doesn't seem to be that simple or I'm having a difficult time wrapping my head around it.
I welcome helpful suggestions, thanks.
I would suggest two options:
1) Create a zone with 'minimal-server' pack installed. Install your application and all dependencies. Create a Unified Archive from that zone. Create a profile for the new zone (with user/password, IP, hostname, etc. -- to avoid doing that at the first boot). Install the zone from that unified archive using the profile you've just created. It's pretty fast--with 'minimal-server' it took me 2-2.5 minutes in VirtualBox. Will be even faster on bare metal.
2) Create an IPS package from your app, publish it on the local repository. Create a manifest where you list 'minimal-server', dependencies and your application package. Install the zone with that manifest and profile (like in the first method).
First method is faster and easier, but it's not very flexible. If you want to change your app, you have to re-create your archive. Second method is more flexible (when you update your app, you just repackage it and publish it one the repository), but it could take longer to install (because individual packages take longer to install than a single archive stream).
Please let me know if you need more detailed instructions and links to the docs.
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed yesterday.
Improve this question
One of web tools we intend to use requires docker for installation. Due to limitation in resources, however, the only way for us to deploy this tool is on a shared university php webserver with an associated MySQL database. My question is, can you somehow convert or even "compile" this docker-dependent tool to get some simple package, similar, for instance, to Wordpress? Indeed, as per my understanding, Wordpress development does require docker, while the final package for Wordpress installation does not.
Is this operation of docker-removal possible and is there a standardised workflow? The tool in question is located in the following repository.
I have tried to install the tool as is, being blocked by the lack of admin privileges and the absence of docker on the described university webserver. I have experience in setting up Wordpress, I would expect for my tool of interest to have a more sophisticated installation process (compared to the current 3 steps) without docker and, for instance, to also require manual connection to an SQL-database.
Please excuse me for my limited understanding and layman terms, I am sadly not coming from a computer science background.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I wanted to get a bit of advice from the StackOverflow community on best practices/guidelines when inheriting a Rails app from another developer.
I am currently in the process of assuming control of development at my place of work. I have decent experience in front-end, SQL/Mongo, and Node.js, and a good amount of knowledge of Ruby. However, I do not have very much experience with Rails, per se.
The previous developer is being fairly unhelpful in providing dependencies and software versions of the various packages in use by the app. However, I have been able to get the following information and I have installed these dependencies (although they may differ from the versions needed by the app):
Postgres
Heroku CLI
AWS CLI
Redis
Sidekiq
AngularJS
Would any of you guys be able to briefly delineate the next steps of getting a previously existing app running (or point me to another source)?
Any help you all can provide is much appreciated. Thank you!
Things you need to retain:
Access credentials to all production servers and used services (including domain name and backup servers if there are any). It is not obligatory to be you, but someone at the company should have them (there may be some security/privacy related issues).
Access to source code
A fresh production backup (if possible)
Most of versions can be inferred from production system once you have full access.
Some others (like sidekiq etc) are in Gemfile.lock and yarn.lock files.
Then try to bring the system up from the backup - if you succeed - you'll be sure that everything is ok
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I'm new to Nix and quite excited about it (I've been using it so far for Haskell).
I'm planning to use it to deploy Php applications. However, how Nix deals with
Php packages (installed normally or with pear).
Working with PHP webapps generally requires several running services (php-fpm, httpd, mysqld, redis, etc). The answer depends on how you manage the services -- which, in turn, depends on whether you use:
(a) The full NixOS: NixOS provides a service-management layer - you edit a config file, twiddle some flags, and turn on the services. I haven't done this myself, and I think it needs a more pointed tutorial for folks coming from a PHP webdev background, but the system does exist.
(b) The crossplatform nix/nixpkgs: There does not appear to be a canonical service-management option here. nix basically just gives some binaries (php-fpm, mysqld, etc) which you can launch yourself. It's somewhat daunting for typical PHP developer.
Full disclosure: To try to improve the situation for crossplatform nix+PHP, I've written an example project locolamp. It won't help much with learning NixOS, but it may help get your toes wet with nix+php in cross-platform usage. See:
https://github.com/totten/locolamp
After spending a week trying to configure a LAMP platform and giving up (mainly because I couldn't make PHP send emails), I concluded that Nix is not ready for developping easily PHP application in production.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
Improve this question
I have several applications that are running 25 hours a day, 7-days a week. They are all web-based, saas applications running on Ruby on Rails. We host our production apps currently on Heroku.
I need a notification system to let me know when the applications are off-line. I know there are a number of options.
I've used Nagios in the past, but it's a bit too configuration intensive for what I need. Also, I'd like an application that I don't host.
Also, I have some worker instances that are running batch jobs. It might be nice to be able to monitor those as well.
It's important that the solution be able to still provide notifications even if Amazon EC2 is down -- so one based on Heroku or Engineyard probably wouldn't work.
OK, based on your initial need --- I would go with either for heroku monitoring. Neither requires SSH to install
http://www.uptimerobot.com/ (checks and emails you when page is not responding) ... I use this and it works well
New Relic Availability http://newrelic.com/features/availability-monitoring --- if you're already using new-relic, just turn this on.
For your worker instances that are running as batch jobs, look at http://www.pushmon.com. You just need to call a URL whenever your batch jobs run successfully. Note I'm associated with PushMon.
We use UptimeRobot for website monitoring.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
Ok, this sounds like a bit of a rant, but I was wondering if there was a technical reason that Erlang doesn't have a proper package management system by default.
No major technical reason really. Just different needs as the classic way of setting up and installing erlang software is though applications. And some use releases added to that.
Often you see erlang software distributed completely self reliant. That is that it contains all the libraries and the virtual machine together in a package and not needing any sorts of external dependencies. You even see this in development versions of packages. The source tree of the Riak database for example has all dependent libraries in it.
This is not a bad idea like many coming from Ruby(like me) may think. This way each application is self reliant. As one of Erlang's main goals is to be the most reliable thing available it makes every sense in the world that each application can have it's own version of the library. Thus making sure one app does not make the other unstable.
Try rebar; it's a build system for erlang that includes a dependency management system. It doesn't have a central repository like gem does with rubygems.org, so you have to specify git urls. But, it does save you the trouble of having to download nested deps; it takes care of that itself.
And it sticks with Erlang's philosophy by keeping the downloaded deps inside your project directory rather then in a central system location; this is similar to bundler's deploy mode.