Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
compose.libre.sh
Manage
Activity
Members
Labels
Plan
Issues
0
Issue boards
Milestones
Wiki
Code
Merge requests
0
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Model registry
Operate
Environments
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
Timothee Gosselin
compose.libre.sh
Commits
b064d85f
Commit
b064d85f
authored
10 years ago
by
Michiel de Jong
Browse files
Options
Downloads
Patches
Plain Diff
improve ubuntu instructions
parent
fb10c71f
No related branches found
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
doc/deploying-a-server.md
+2
-1
2 additions, 1 deletion
doc/deploying-a-server.md
doc/running-on-ubuntu.md
+2
-2
2 additions, 2 deletions
doc/running-on-ubuntu.md
with
4 additions
and
3 deletions
doc/deploying-a-server.md
+
2
−
1
View file @
b064d85f
...
...
@@ -4,7 +4,8 @@
Make sure you read
[
getting started
](
getting-started-as-a-hoster.md
)
first.
### Prepare your orchestration data
*
Get a CoreOS server, for instance from
[
RackSpace
](
rackspace.com
)
or
[
Vultr
](
vultr.com
)
.
*
Get a CoreOS or Ubuntu server, for instance from
[
RackSpace
](
rackspace.com
)
or
[
Vultr
](
vultr.com
)
.
*
If you chose Ubuntu, follow the
[
Ubuntu-specific
](
running-on-ubuntu.md
)
instructions, then continue here.
*
If you didn't add your public ssh key during the order process (e.g. through your IaaS control panel or a cloud-config file),
scp your laptop's public ssh key (probably in
`~/.ssh/id_rsa.pub`
) to
`.ssh/authorized_keys`
for the remote user
you will be ssh-ing and scp-ing as (the default remote user of our deploy scripts is 'core').
...
...
This diff is collapsed.
Click to expand it.
doc/running-on-ubuntu.md
+
2
−
2
View file @
b064d85f
...
...
@@ -6,12 +6,13 @@ dpkg-reconfigure -plow unattended-upgrades
# set unattended upgrades to 'Yes'
apt-get
-y
install
systemd-sysv git docker.io
printf
'#!/bin/sh\ndocker run --net=host quay.io/coreos/etcd:v0.4.6 /etcdctl $1 $2 $3 $4'
>
/usr/local/bin/etcdctl
chmod
u+x /usr/local/bin/etcdctl
printf
"[Unit]
\n
Requires=docker.service
\n
After=docker.service
\n
[Service]
\n
Restart=always
\n\
ExecStartPre=-/usr/bin/docker kill etcd
\n\
ExecStartPre=-/usr/bin/docker rm etcd
\n\
ExecStart=/usr/bin/docker run
\
--name etcd
\
-p 4001:4001
\
-p
127.0.0.1:
4001:4001
\
quay.io/coreos/etcd:v0.4.6
\n\
ExecReload=/usr/bin/docker restart etcd
\n\
ExecStop=/usr/bin/docker stop etcd
\n\
...
...
@@ -29,6 +30,5 @@ etcdctl ls
etcdctl help
````
Be aware that this will expose etcd on port 4001, also on the public IP address, so if you are using this in production the it is very important to block this port on the firewall.
Now follow the
[
CoreOS-based instructions
](
deploying-a-server.md
)
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