issues
search
futurice
/
backend-best-practices
An evolving description of general best practices for backend development.
Other
2.07k
stars
259
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Turkish Translation
#20
umutphp
closed
5 years ago
3
Add some notes about Docker security
#19
kimmoahokas
closed
5 years ago
0
RFC: 2018 revision.
#18
jarcane
closed
5 years ago
0
Responsibility go-live checklist for website projects
#17
tino-junge
closed
8 years ago
2
Under Anonymized Data: added few lines about sensitive logs.
#16
riihela
closed
8 years ago
0
Added a section for bad monitoring examples
#15
laurianttila
opened
8 years ago
5
Futurice/english checking
#14
ekantola
closed
9 years ago
1
Add monitoring guidelines
#13
bladealslayer
closed
9 years ago
0
Persistence
#12
ilkka
closed
9 years ago
0
Reword dev env setup, add docker-compose
#11
ilkka
closed
9 years ago
0
Add Testing env, split CI into CI and Staging
#10
ilkka
closed
9 years ago
1
Add staging to minimum recommended environments
#9
olliahonen
closed
9 years ago
4
Add link to relevant password-hashing material
#8
olliahonen
closed
9 years ago
0
maximum allowed downtime
#7
petrukhnov
closed
9 years ago
1
Add HTTPie and jq as tool recommendations
#6
ilkka
closed
9 years ago
0
Missing: Concrete description of OS-level runtime environment (in production)
#5
olliahonen
opened
9 years ago
2
Write release checklist
#4
ilkka
closed
9 years ago
2
Rewrite list of environments
#3
ilkka
closed
9 years ago
0
link to site explaining why to use UTC everywhere
#2
villesinisalo
closed
9 years ago
2
Add a stub section about security. Just two links to general checklists.
#1
jkalfutu
closed
9 years ago
3