You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-32Lines changed: 6 additions & 32 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,11 +40,8 @@ designed to make coding as simple and fun as playing a video game.
40
40
4. Uncompromised local development experience.
41
41
5. Support for pluggable remote back-ends.
42
42
6. Phoenix core will work from a static web server.
43
-
7. Source code in release builds will always be auditable and readable from dev-tools.
44
-
45
-
AGPL/Libre license guards your right to audit and change code that handles your data.
46
-
Phoenix usually loads up in under one second and loading it faster at the expense of making it hard
47
-
to read and develop is a noop. We prioritize simplicity and eaze of development.
43
+
7. Compile step less build process. Code changes in phoenix do not need to be recompiled for most cases for development.
44
+
8. Prioritize simplicity and ease of development.
48
45
49
46
## Contributing/ Feedback
50
47
*[Get in touch with our community](https://github.com/phcode-dev/phoenix/discussions).
@@ -111,10 +108,10 @@ It has much better debug UX and fixing it directly in the browser will almost ce
111
108
2. Run the unit tests using format: `npm run test<*>Dist`. Eg. `npm run testChromiumDist`.
112
109
3. Run the integration tests using the format: `npx cross-env TEST_ENV=<integration suite name> npm run test<*>Dist`. Eg. `npx cross-env TEST_ENV=mainview npm run testChromiumDist`.
113
110
114
-
#### To run tests against these stacks go to the following url:
#### To run tests against these dev/staging/prod in the browser
112
+
1. Build the release using `npm run release:<stage>`. Eg: `npm run release:dev`
113
+
2. Run `npm run serve` to start the server.
114
+
3. Go to `http://localhost:8000/dist-test/test/SpecRunner.html` in the browser to run tests that was built for the stage above.
118
115
119
116
## Browsing the virtual file system
120
117
To view/edit the files in the browser virtual file system in Phoenix:
@@ -123,39 +120,16 @@ To view/edit the files in the browser virtual file system in Phoenix:
123
120
## Clean and reset builds
124
121
* clean builds only: `npm run clean`
125
122
126
-
## Previewing changes in dev and staging
127
-
One a pull request is merged, it will be automatically deployed to dev.phcode.dev . To view the changes:
128
-
1. goto https://dev.phcode.dev/devEnable.html and click `enable dev.phcode.dev` . only needs to be done once.
129
-
2. goto https://dev.phcode.dev to preview your changes. If it is a recent change, you might need to wait for
130
-
up to 15 minutes before the changes are deployed to the dev stage. Reload page a few times to get the latest
131
-
dev build and reset cached content.
132
-
133
-
The process is the same for `staging.phcode.dev`. Builds that are verified in development will be pushed
134
-
periodically to staging. To view staging:
135
-
1. goto https://staging.phcode.dev/devEnable.html and click `enable staging.phcode.dev` . only needs to be done once.
136
-
2. goto https://staging.phcode.dev to preview your changes. If it is a recent change, you might need to wait for
137
-
up to 15 minutes before the changes are deployed to the dev stage. Reload page a few times to get the latest
138
-
dev build and reset cached content.
139
-
140
-
## Deployment to phcode.dev
141
-
* All changes pushed to the main branch are automatically published to https://dev.phcode.dev
142
-
* To publish the changes to https://staging.phcode.dev , push changes to the `staging` branch in this repo with a pull request.
143
-
* Once the changes are validated and tested, trigger a prod deployment by pushing to the `prod` branch.
144
-
145
123
## Acknowledgements
146
124
* Phoenix is based on the Brackets code editor by Adobe. Find out more on [Adobe Brackets here](https://github.com/adobe/brackets/).
147
125
* Our main code editor library https://codemirror.net/
148
126
* Inspired by previous work from the [Mozilla Thimble](https://github.com/mozilla/thimble.mozilla.org) project to port brackets to the web. https://github.com/mozilla/brackets
149
127
* In browser server based on [nohost](https://github.com/humphd/nohost) by https://github.com/humphd/
0 commit comments