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
* Added to FAQ page
* chore(monorepo): update to latest NX && Angular
* chore(monorepo): update deps to latest versions
* docs(docsWeb): add roadmap, consultancy and form for adding links.
* chore(monorepo): update workflow to represent V2 version compatability
* Update docs/consutancy.md (Co-authored-by: Jeffrey Bosch <[email protected]>)
* Update docs/faq.md(Co-authored-by: Jeffrey Bosch <[email protected]>)
* chore(monorepo): u[date peerdeps for new versions
* chore(monorepo): use the force, to test node versions that aren't on Angulars supported list
* chore(Actions): update workflow for node 14/16
* docs(docsWeb): accenturate the optional nature of render plugins
* chore(monorepo): update package versions to match release(Co-authored-by: Jeffrey Bosch <[email protected]>)
Copy file name to clipboardexpand all lines: README.md
+4
Original file line number
Diff line number
Diff line change
@@ -44,6 +44,10 @@ those who want to know more about the theory behind pre-rendering JavaScript SPA
44
44
wrote a [free book about the Jamstack](https://www.netlify.com/pdf/oreilly-modern-web-development-on-the-jamstack.pdf).
45
45
Check that out today.
46
46
47
+
> ### NOTE!
48
+
> Please notice that with the release of Scully version 2, support for Angular versions lower as 12 is deprecated.
49
+
> for older versions, you can keep on using the existing 1.1.1 version, which will only receive security updates from now on.
50
+
47
51
#### GET A HOLD OF US 24/7
48
52
49
53
The Scully core team wants to help you any time you need us. We don’t want you to get stuck without help. To make this possible, you have the following ways to get a hold of our team:
Copy file name to clipboardexpand all lines: docs/faq.md
+43
Original file line number
Diff line number
Diff line change
@@ -222,6 +222,49 @@ Also, make sure you add the following to your config:
222
222
223
223
</details>
224
224
225
+
<details>
226
+
<summary>Scully inside GCE has timeout failures.</summary>
227
+
228
+
It seems that inside GCE sometimes the server takes a long time to properly come up. If this happens, you can extend the waiting time for the server with a command-line parameter like:
In here we are listing the things we would like to implement in Scully.
11
+
We are giving no time-estimates as we are deppening on available time of contributors and/or sponsors.
12
+
There are an couple of new optional render plugins in the list. Those will all be optional, the current way of working will keep on existing. We plan on changing the default renderer to the playwright version when we have enough feedback and testing done. Even when this happens, you can still keep on using the system that is now in place, and the new default will only be activated in new projects.
13
+
14
+
- release V2 of Scully
15
+
- Deprecate support for Angular before version 12.
16
+
- V2 will require Angular v12 and up
17
+
- V2 will switch over to the new Ivy library structure soon
18
+
- V1 will remain available for Angular versions 9/10/11
19
+
- support for versions before V9 is completely dropped.
20
+
- Better control over server-start-stop.
21
+
- We have had some reports of stalling in CI/CD, an this seems to be the root cause of this issue.
22
+
- optional Renderer build on top of [platform-server](https://angular.io/api/platform-server)
23
+
- Scully is now using Puppeteer to render the resulting pages. This approach will be using the platform server. While this puts some additional demands on the application (similar to Angular Universal, which uses the same engine), it can render pages _much_ faster. (It doesn't have to start a browser, navigate to a page and so on)
24
+
- optional Render build on top of [Playwright](https://github.com/microsoft/playwright)
25
+
- This is very similar to Puppeteer, but supports more browsers, and works on M1 chips.
26
+
- optional Platform server renderer with auto fallback.
27
+
- will first try the platform-render, and if that fails uses another renderer to finish the page.
28
+
- this will allow sites that are not build with the restrictions of the platforms-server in mind to slowly migrate.
29
+
- Build On Demand server
30
+
- This will be a server, where you call into to have Scully build pages on demand.
31
+
- When called with a route, it will return the index.html for that route.
32
+
- It can optionally write it to disk.
33
+
- It can optionally call a script. This might be used to deploy the route
34
+
- Extended BOD server. (see right above)
35
+
- Provide webhooks for CMS systems to inform for updated dependencies
36
+
- uses the cache plugin to build a dependencies map
37
+
- will use that map to rerender the pages that are touched by the updated dependency.
38
+
- will provide a way to manually add linked deps. (if x updates, render y)
39
+
- Monitoring server.
40
+
- this will be a server that you can use to monitor your CMS(es) and/or DB's and then kicks off the Extended BOD functionality to deploy the updated routes
41
+
- Hybrid SSR server on top of the platform-server renderer.
42
+
- this extends the BOD server with:
43
+
- a way to handle sites with a mixture of dynamic session pages and static ones
44
+
- static pages will be prerendered, and served fully static
45
+
- dynamic-session pages will be rendered on demand.
46
+
47
+
When you want us to give any of those priority, check our [consultancy page](./consutancy.md). The team at HeroDevs will gladly help you.
0 commit comments