|
What's a good way to write out a software spec for a webapp? I've written out the relevant parts out of IEEE830 but there's probably a better way to do it. I'm going to outsource some coding locally and would like something easily understandable to show potential contractors. Should I just write out url routes and describe what they are supposed to do?
|
#
¿
Jul 19, 2013 14:06
|
|
|
|
| # ¿ May 2, 2024 00:55 |
|
|
This is a bit off topic but does anyone have any recommended readings on how to properly configure, deploy and tune web servers/databases? I've developed an intranet based web application that has to be deployed on site in many different locations but I only have coding experience. I have the freedom to install it on any hardware I see fit.
|
|
#
¿
Jan 3, 2014 17:13
|
|
|
What is the current state of "serverless" nowadays? I'm looking to start up a web project with your standard free and paid subscription tier model, so it will have user registration, authentication with JWT tokens, different access to URLs/resources, monthly billing etc. Is is possible to build this using just cloud functions+S3+noSQL? Or would the minimum be choosing a framework and deploying on AWS Elastic beanstalk / Google App Engine?
|
|
#
¿
Mar 17, 2018 14:10
|
|