Ideally, they should give you a mini-monster server so you could spin up
your own VMs or run Docker. Actually, Docker would be a great way to go. I
would want at least 8 GB RAM and 4 cores, although I would ask for at least
Of course, in my world, I would just spin up nano and micro instances on
AWS as I needed them. I run scripts to turn them off when they are not
being used. If you need to test on bigger hardware, use spot instances.
If hardware is free for you, then you'll be sticking to it, I presume.
On Thu, Aug 2, 2018 at 1:56 PM, Julie Cole <[log in to unmask]> wrote:
> Good point, although in a VM environment it is likely outside our control,
> and might be hard to justify an exception for a sandbox server.
> -----Original Message-----
> From: Code for Libraries <[log in to unmask]> On Behalf Of Edward
> Sent: Thursday, August 2, 2018 1:19 PM
> To: [log in to unmask]
> Subject: Re: [CODE4LIB] Web Server Specs?
> On Aug 2, 2018, at 2:27 PM, Julie Cole <[log in to unmask]> wrote:
> > We plan to install a LAPP or LAMP stack on it. (maybe both databases?)
> I don't see this as being a very heavy transaction oriented environment.
> Some thoughts of things we would like to do with it:
> > This will likely be a virtual server, so it won't be written in stone,
> but I'm still unclear on how much to ask for in terms of CPU, Memory and
> > Any tips, pointers, gotchas?
> If possible, get an SSD for storage. In addition to the obvious increased
> general responsiveness, it’ll make many development and maintenance tasks
> far less onerous.
> Edward Almasy <[log in to unmask]>
> Director • Internet Scout Research Group Computer Sciences Dept • U of
> Wisconsin - Madison
> 1210 W Dayton St • Madison WI 53706 • 3HCV+J6
> 608-262-6606 (voice) • 608-265-9296 (fax)
The Cherry Hill Company