A public channel for the Angular community to come talk about Scully and JAMStack strategies in Angular.
Hello Everyone,
I have been tasked to create a website for 5 apartments that will be used for holiday lets.
I've been working in Angular for a while and enjoy it, but in this case SEO is a major concern, so I thought I could give scully a try.
I would like to get some advice on a possible stack to implement this,
Would this be a good starting point/idea:
Angular/Scully
Firebase for db
Snipcart/Stripe for checkout
Anybody know any good booking libraries of sorts? Would you just implement your own with something like full calendar?
Thank you
Edit:
Maybe could use strapi instead of firebase, never used it for more than a blog but maybe it's flexible enough
Hello, in a strange coincidence I have almost the exact situation as @sanjay51 of needing dynamic content.
The use case is for the user to be able to bookmark dynamic page. Originally I had been using params but scully, as designed, doesn\'t render that page giving the expected
No configuration for route "/path/:id" found. Skipping
And then if you ignore this route you run into the issue observed in @sanjay51 stackoverflow issue.
I thought then why not switch to query parameters. It sort of worked. Scully seems to parse out the trailing forward slash. If you have a url with a forward slash followed by the quesiton mark all works fine since only the forward slash is removed leaving the query params. If you do not have the forward slash all the query params are removed ie:
.../stuff/?id=l1w70y5l turns into .../stuff?id=l1w70y5l and works, but.../stuff?id=l1w70y5l turns into .../stuff and clearly breaks since there is no query params to read.
I have read through old git hub issues and even searched this chat and i see where @SanderElias states that query params don\'t play nice with JAM stack. I agree and wasn\'t my first choice as stated above. I have no issue changing my architecture if it solves my issue. Thanks in advanced
18 replies
@mrwaffles143_twitter I posted a solution that uses firebase hosting config to configure the URL path <--> index.html mapping, please take a look if it applies to your case. Thanks.
2 replies
What are the differences between
Scully platform server,pupeteer and playwright?
@griffinguy:matrix.org Angular universal uses platform server, and I had some issues with it as I was using properties of window and localhost objects in my application. When I switched to scully, puppeteer worked very well for me.
I heard though that platform-server is faster, as it doesn't require rendering pages in an actual browser - https://scully.io/docs/roadmap/
Platfrom server uses indeed the Angular Platform server, and while we made it a bit better, it might have some issues for your application. But its much faster.
playwright can work with different browsers, which might be a requirement for some project.
Also, it doesn't load the route when I reload the page but works when I navigate to it.
1 reply
Also, it doesn't load the route when I reload the page but works when I navigate to it.
could this be the issue
CREATE AN ENTRY POINT (HOME PAGE)
1 reply
diff highlighting with prismjs like in the code snippets in this blog post https://www.netlify.com/blog/2020/07/14/creating-an-angular-jamstack-blog/
In my app I have a "/about" page, also if someone goes to root path, it is redirected to "/about" page, In scully server this is working fine but when i refresh "/about" page, it gives status 301 and redirects to "/about/" ? can't figure out why so, in normal angular app on refresh there is no such redirection.
It is set up in such a way that it will expose all common problems you might encounter while you deploy your app.
Also it is set up to have really loose security, which is good for dev, but very bad for production. The warning that its not an production server is there not for nothing
4 replies
By default Scully uses the core-count of a machine for the number of threads.
I recently upgraded from Angular 11 to 13, but running npx scully seems to take an abnormally long time now to generate routes. I can't seem to find anything in this chat, the github, or even starting a new project and copying more recent scully settings doesn't seem to fix it. The renderer is puppeteer and one of our routes does use the resultsHandler to bring in some blog posts if that helps. Here's the time it took:
Total time used 213.38 seconds
44 pages have been created
Rendering the pages took 208.38 seconds
That is 0.22 pages per second,
or 4736 milliseconds for each page.This used to take around 60-90 seconds, which is more than double the time now
"pageImageId": 1,
"createdOn": "2022-05-05T16:19:06.6071658",
"updatedOn": "2022-05-05T18:16:31.1928573",
"isImageNameChanged": false,
"pageTagId": 1,
"pageRoute": "~s~",
"imageFolder": "assets~s~img~s~static-web-page~s~home",
"imageName": "banner",
"imageTitle": "banner",
"imageAltText": "banner",
"imageKey": "homebanner",
"imageCaption": "banner"
}, {
"pageImageId": 5,
"createdOn": "2022-05-05T17:04:17.9482594",
"updatedOn": "2022-05-05T18:16:17.1815576",
"isImageNameChanged": false,
"pageTagId": 1,
"pageRoute": "~s~",
"imageFolder": "assets~s~img~s~static-web-page_~s~home",
"imageName": "softie-create",
"imageTitle": "softie create",
"imageAltText": "softie create",
"imageKey": "homesoftie-create",
"imageCaption": "softie create"
}, {
"pageImageId": 6,
"createdOn": "2022-05-05T17:05:15.910535",
"updatedOn": "2022-05-06T12:31:11.1497415",
"isImageNameChanged": false,
"pageTagId": 1,
"pageRoute": "~s~",
"imageFolder": "assets~s~img~s~static-web-page_~s~home",
"imageName": "softie-selfie",
"imageTitle": "softie selfie",
"imageAltText": "softie selfie",
"imageKey": "homesoftie-selfie",
"imageCaption": "softie selfie"
}, {
"pageImageId": 7,
"createdOn": "2022-05-05T17:06:33.8791868",
"updatedOn": "2022-05-05T18:16:40.8563212",
"isImageNameChanged": false,
"pageTagId": 1,
"pageRoute": "~s~",
"imageFolder": "assets~s~img~s~static-web-page_~s~home",
"imageName": "softie-creator-pack",
"imageTitle": "softie creator pack",
"imageAltText": "softie creator pack",
"imageKey": "home_softie-creator-pack",
"imageCaption": "softie creator pack"
}
