Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
S
slapos.buildout
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Xavier Thompson
slapos.buildout
Commits
d6dc0e03
Commit
d6dc0e03
authored
Feb 02, 2018
by
Nils Diefenbach
Committed by
GitHub
Feb 02, 2018
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix a typo, minor grammar issues
parent
97003f82
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
doc/index.rst
doc/index.rst
+3
-3
No files found.
doc/index.rst
View file @
d6dc0e03
...
...
@@ -25,7 +25,7 @@ It's important that given a project configuration, two checkouts of the
configuration in the same environment (operating system, Python
version) should produce the same result, regardless of their history.
For example, i
s
someone has been working on a project for a long time,
For example, i
f
someone has been working on a project for a long time,
and has committed their changes to a version control system, they
should be able tell a colleague to check out their project and run
buildout and the resulting build should have the same result as the
...
...
@@ -34,7 +34,7 @@ build in the original working area.
Componentization
================
We believe that software should be self
contained, or at least, that
We believe that software should be self
-
contained, or at least, that
it should be possible. The tools for satisfying the software
responsibilities should largely reside within the software project
itself.
...
...
@@ -58,7 +58,7 @@ Automation
==========
Software deployment should be highly automated. It should be possible
to checkout a project
and with a single simple command (or two),
get a
to checkout a project
with a single simple command (or two) and
get a
working system. This is necessary to achieve the goals of
repeatability and componentization and generally not to waste people's
time.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment