blob: 48d8cb0655886ebff837173645937a4b9f6cf0fc (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
---
layout: page
title: Updating an AMI installation
---
# Updating an AMI installation
<p class="lead">Let's say you set up an EC2 instance from our AMI when FixMyStreet was on
version 2.0, and you now want to upgrade to version 2.1. This page should
help.</p>
(If you forked the code on GitHub and cloned it yourself, you probably want to see our
main [update help](/updating/).)
Firstly, log in to your EC2 instance as the `ubuntu` user, as you did when
setting up the instance. You should become the fms user and switch to the right
directory:
ubuntu@ip-10-58-191-98:~$ sudo su - fms
fms@ip-10-58-191-98:~$ cd fixmystreet
fms@ip-10-58-191-98:~/fixmystreet$
To fetch new upstream code, but not yet use it, use:
fms@ip-10-58-191-98:~/fixmystreet$ git fetch origin
Then merging the new version of the upstream code into your version will bring
your code up-to-date. You can do that with:
fms@ip-10-58-191-98:~/fixmystreet$ git merge v2.1
If you have made alterations to your local repository, then you will need to
make sure they are all committed to your local branch and fork first, see
[setting up a fork](/feeding-back/) for more information. You may want
to try checking out your repository elsewhere and trying the merge there first,
to see if it there are any problems.
After updating the code, you should run the following command to update any
needed dependencies and any schema changes to your database. It's a good idea
to take a backup of your database first.
fms@ip-10-58-191-98:~/fixmystreet$ script/update
If you have made changes to the schema yourself, this may not work,
please feel free to [contact us](/community/) to discuss it first.
Lastly, you should restart the Catalyst FastCGI server with:
fms@ip-10-58-191-98:~/fixmystreet$ logout
ubuntu@ip-10-58-191-98:~$ sudo /etc/init.d/fixmystreet restart
|
