Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

jminkler's avatar

Installing Spark site on Forge

Recently purchased Spark, and am now trying to deploy the code with Forge but am getting stuck pulling down the private repo. How to allow the forge site access to the code?

0 likes
8 replies
jekinney's avatar

???

You install spark locally then push to your git or server.

1 like
fwartner's avatar

But do not forget that you have to set your repository to private when using git for deployment. Otherwise Taylor may handles your spark-key as fragile or something..

jminkler's avatar

No, Spark is part of the project's composer, project is on private bitbucket, when it gets to forge, with the Spark repository in composer, it fails (box doesn't have rights?) Do I need to install spark on the forge box and register the token again? In other words, I installed spark locally to build project, but now how can I get it up to forge.

tptompkins's avatar

@jminkler Did you ever make any progress with this? I'm going to be deploying my Spark code soon and was curious if I'm going to run into any hiccups with the deployment. Any tips would be appreciated. Thanks!

jminkler's avatar

I think I just have to install spark on the forge machine and register the token. Haven't tried it yet.

undrwd's avatar

I'm running in to this issue. Moving to Spark 2.0 I added it to my composer so adding the repo in spark appears to be encountering an error and won't add the repo. When running composer update locally it gave me a URL to generate and enter a git key for access to the private spark repo. I expect the same thing is required on my droplet but since it can't mount the repo I can't ssh in and run composer update. Any advice to get past this?

undrwd's avatar
undrwd
Best Answer
Level 5

ok, it was simple as expected.

When adding your repo in forge uncheck the MAGIC Install Composer Dependencies option, then it will mount your repo and you can ssh in and run composer update and paste in the same GitHub key you generated for local dev to authorize access to the private spark repo and everything will run normally.

1 like
jminkler's avatar

Thanks, I switched gears, and hadn't tried it yet.

Please or to participate in this conversation.