Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
ots-www
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
azacr
ots-www
Commits
f6f051bf
Commit
f6f051bf
authored
3 years ago
by
Karl Fogel
Browse files
Options
Downloads
Patches
Plain Diff
Formatting fixes to README.md
parent
35fd5489
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+14
-15
14 additions, 15 deletions
README.md
with
14 additions
and
15 deletions
README.md
+
14
−
15
View file @
f6f051bf
...
...
@@ -12,34 +12,33 @@ Source URL: https://code.librehq.com/ots/ots-www
now; let's be New Hotness, not Old 'n Busted).
*
But right now we only have one top-level HTML file anyway, "home",
and the .htaccess file names it as the default DirectoryIndex.
and the
`
.htaccess
`
file names it as the default DirectoryIndex.
Speaking of which:
*
We have a top-level .htaccess file. If you create a new page,
remember to enter it in the obvious place in .htaccess.
*
We have a top-level
`
.htaccess
`
file. If you create a new page,
remember to enter it in the obvious place in
`
.htaccess
`
.
*
If you need to make materials available privately to a specific
client, put them in the files/ subdirectory, which is on the web
server and is versioned separately in the
`bigdata`
repository,
as
described below.
client, put them in the
`
files/
`
subdirectory, which is on the web
server and is versioned separately in the
`bigdata`
repository,
as
described below.
# Putting things in
http://opentechstrategies.com/files/
# Putting things in
the `files/` subdirectory
We put docs and artifacts for people to download in
http://opentechstrategies.com/files/, usually in either the pub/
subdirectory or the presentations/ subdirectory, but sometimes in a
http://opentechstrategies.com/files/, usually in either the
`
pub/
`
subdirectory or the
`
presentations/
`
subdirectory, but sometimes in a
client-specific subdirectory. Client-specific subdirectories may be
access-controlled with a .htaccess file; if you want, you can use the
svn.red-bean.com/repos/kfogel/trunk/bin/web-password-protect-directory
to automate that process, but it's easy to do by hand too.
access-controlled with a
`
.htaccess
`
file; if you want, you can use the
[
web-password-protect-directory
](
https://
svn.red-bean.com/repos/kfogel/trunk/bin/web-password-protect-directory
)
script
to automate that process, but it's easy to do by hand too.
The files/ tree is versioned in the
`bigdata`
repository (which you
The
`
files/
`
tree is versioned in the
`bigdata`
repository (which you
only have version-controlled access to if you're associated with OTS).
To see details about why and how, read the README there:
```
$ svn cat \
https://svn.opentechstrategies.com/repos/bigdata/trunk/www/files/README
$ svn cat https://svn.opentechstrategies.com/repos/bigdata/trunk/www/files/README
```
# Deploying
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment