Closed
Bug 1223032
Opened 10 years ago
Closed 10 years ago
Need hosted Dev Environment for Splice
Categories
(Content Services Graveyard :: Tiles: Ops, defect)
Content Services Graveyard
Tiles: Ops
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: tspurway, Assigned: relud)
Details
We would like to be able to manually deploy splice code to a hosted environment. This environment would resemble our current staging environment, though we could possibly get away with using a single RDS instance for both of our databases.
Initially, we would like to be able to deploy to the instance 'manually' - eventually we would like to build in CI hooks to automatically build and deploy what is on the master branch.
| Assignee | ||
Updated•10 years ago
|
Assignee: nobody → dthorn
Status: NEW → ASSIGNED
| Assignee | ||
Comment 1•10 years ago
|
||
Splice is deployed in dev
ssh access with:
ssh bastion.shared.us-east-1.dev.mozaws.net -t ssh splice_tiles.stage.mozaws.net
http access over vpn (pending 1223151) with:
http://splice_tiles.stage.mozaws.net
continuous deployment needs a couple more things before it's ready, will update when it's working.
| Assignee | ||
Comment 2•10 years ago
|
||
continuous deployment is configured, and working. If you would like me to deploy the sp2 branch, then it needs to be pushed to mozilla/splice (as opposed to oyiptong/splice).
| Reporter | ||
Comment 3•10 years ago
|
||
Thanks, :relud!
I pushed the `sp2` branch to mozilla/splice. Can you switch over the config to that? There are also migrations in that branch that need to run, but i could probably do those?
| Reporter | ||
Comment 4•10 years ago
|
||
I am also trying to ssh to the node with:
ssh bastion.shared.us-east-1.dev.mozaws.net -t ssh splice_tiles.stage.mozaws.net
but the connection seems to be timing out. I am connected to the VPN when I issue the command
| Assignee | ||
Comment 5•10 years ago
|
||
figured it out in irc, but notable: you don't need to be on vpn for ssh.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•