Skip to content

Fixed typos #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 3, 2016
Merged

Fixed typos #22

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion documentation/DOCKER-INFO.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -106,4 +106,4 @@ Save, set a break point and test the debugger.
## Application cache

Symlink your application cache (eg. typo3temp/) to `/data/cache/` and it will be stored inside the `storage` container
so it will be accessable within all containers (eg. web or main).
so it will be accessible within all containers (eg. web or main).
4 changes: 2 additions & 2 deletions documentation/DOCKER-STARTUP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,10 +27,10 @@ For an existing project just put your files into `code/` folder or use git to cl
## Advanced usage (git)

Use this boilerplate as template and customize it for each project. Put this Docker
configuration for each project into seperate git repositories.
configuration for each project into separate git repositories.

Now set your existing project repository to be a git submodule in `code/`.
Every developer now needs only to clone the Docker repository with `--recursive` option
to get both, the Docker configuration and the TYPO3 installation.

For better useability track a whole branch (eg. develop or master) as submodule and not just a single commit.
For better usability track a whole branch (eg. develop or master) as submodule and not just a single commit.
6 changes: 3 additions & 3 deletions documentation/INSTALL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

# Installation

## Reqirements
## Requirements

- GNU/Linux with Docker (recommendation: [Vagrant](https://www.vagrantup.com/downloads.html) VM with Docker or [native Linux with Docker](http://docs.docker.com/linux/step_one/)
- make
Expand All @@ -15,8 +15,8 @@ the much faster virtualisation (networking, disk access, shared folders) compare
There is also a [Vagrant VM for VirtualBox, VMware and Parallels](https://github.com/webdevops/vagrant-docker-vm)
with a mailcatcher (Postfix with Dovecot, catches all outgoing mails).

_Warning:_ Boot2docker ist not recommended because of slow/buggy file sharing between host and guest and there is no
convienient way to access the box with Samba or SSH.
_Warning:_ Boot2docker is not recommended because of slow/buggy file sharing between host and guest and there is no
convenient way to access the box with Samba or SSH.
This Docker boilerplate tries to avoid common anti-patterns like a Samba/SSH container because Boot2docker
isn't able to handle such tasks.

Expand Down