Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    iiceman40
    @iiceman40
    If I add it to the args it doesn't throw an error, but I don't see any browser.
    Sander Elias
    @SanderElias
    options are the puppeteerLaunchOptions directly from the config.
    So, if it doesn't show the browser, I don't have a clue for now. I need to be able to reproduce the issue.
    (BTW, I'm on linux, and don't have access to windows right now)
    those options are fed verbatim to puppeteer, I'm not dong anything else with those.
    iiceman40
    @iiceman40

    If I set the healess flag directly in the puppeteerLaunchOptions like this:

     puppeteerLaunchOptions: {
        executablePath: '/usr/bin/chromium-browser',
        headless: false,
        ...

    It throws the same error... what makes sense since you said that the --showBrowser flag actually does the same thing. I guess it really is the Docker or the WSL2 that's causing the error.

    I guess I will check the project out directly in my Windows environment to see if the error occurs without WSL2 and without Docker.
    Thanks again for the quick feedback! :)
    Sander Elias
    @SanderElias
    Your welcome. Puppeteer is sometimes hard to get up and running. We try to take care of most things, but we can't fix all :)
    iiceman40
    @iiceman40
    I got it to run directly under Windows now and trying to find out why it doesn't render the content. It seems there is always just that empty <router-outlet> ... it's kinda hard checking things out if it opens alot of tabs at once... is there a command line option to render only a certain route? (I saw something about ignoring routes, but can I set a certain route that I want to render?)
    George Kayzer
    @Niaro
    image.png
    @SanderElias Hello! Thanks for the awesome tool! But I'm experiencing weird stuff, when on the scully config I refer a plugin and execute scully the ts files inside the plugins folder don't get compiled thus when scully executes it doesn't see the modules
    I created a new nx workspace with angular, and added through the cli scully
    How the Scully plugins get compiled? Should I do it manually now?
    Sander Elias
    @SanderElias
    @Niaro You should not be using the .scully folder, but instead the ./scully folder for your plugins.
    Scully will use the tsconfig in the ./scully folder to compile the plugins you did put in there.
    @iiceman40 when you add the --showRotues cmd line option, the tabs stay open way longer. Also you can reduce the max-render-threads in the config, if you set it to 1, then its using only 1 tab
    George Kayzer
    @Niaro
    @SanderElias but I refer plugins' symbols in the scully config file for the sake of not using magic constants
    image.png
    It was working fine, till some moment ago
    George Kayzer
    @Niaro
    And weirdly enough, if just to use a plugins name on the config, the plugin doesn't get compiled, and doesn't affect the scully build
    Everything latest, nx and scully
    win10
    Sander Elias
    @SanderElias
    you can use a plugin in any folder, but you need to manually compile it. as you are using ./.scully instead of ./scully you need to do this.
    when everything is in the ./scully folder, and you didn't change the tsconfig in there, it should compile just fine.
    George Kayzer
    @Niaro
    @SanderElias So if I use a custom plugins folder I need to compile it? and provide it with --pluginFolder
    Weird enough it was working)) I didn't compile the custom scully plugins folder before.
    George Kayzer
    @Niaro
    To not pollute the root of the workspace I keep the apps` scully configs inside the app folder, and the plugins usually related to the app to since they do just fetching...
    George Kayzer
    @Niaro
    @SanderElias Anyway thanks a ton for the clarification) At least I can proceed))
    George Kayzer
    @Niaro
    @SanderElias btw what is the use case for the scully-plugin-local-cache ?)
    Sander Elias
    @SanderElias
    Speed up your build, and stop ddos ing your API servers.
    Also, I can't explain why it was working before, as this never changed. You can add a custom folder to the tsconfig in the ./scully folder, and have it automatically compiled tho. it's not there by default (and never was)
    Also, you can author plugins in JS, and then there is no need for compilation.
    Karen
    @ks510
    Hey, I'm new to using Scully and I was hoping to get some help on using it with a localised Angular app (using Angular i18n) for 2 languages (en and de). I followed this tutorial on dev.to and managed to successfully run Scully with the bash script but I can't figure out how to serve the generated pages to check if it worked correctly. What params do I need to add to npm run scully:serve to set which locale it should serve?
    iiceman40
    @iiceman40
    @SanderElias Hi again :) I think I am starting to get the hang of it... currently I am writing a router plugin to let scully know what route paramters to use to render my detail pages. Is there a way to access the current parameters in one of my plugins? I am calling the scully with the hostName parameter and I need the hostName in my plugin, too, to query the available ids for this host from our backend. Is this possible?
    Erin
    @hchings

    Does anyone have used Scully on a cloud instance (Linux)? When running "npx scully --scanRoutes" on a CD server in AWS, the "Rendering Route" process is extremely slow, and based on the speed, it will take hours before we can finish pre-rendering 300 routes.

    The speed was fine when we run on local. Can this be improved with Chromium settings? If yes, which settings should be used? Thanks in advance

    Joey McKenzie
    @JoeyMckenzie
    Afternoon folks. Was recently integrating Netlify CMS into a site for a client and ran into a weird issue. Following scullyio/scully#1281 and everything seems to work fine, although the only issue I'm facing is this sort of login screen appearing twice. Running my app as a normal Angular app, this doesn't seem to happen. I'm rather new to Scully, so I'm curious to see if anyone has run into this issue before.
    For refence, kind of hard to see:
    image.png
    This seems to be the case when running the sample listed in the PR as well, anytime when running the app with Scully rather than the normal Angular bootstrapping. Just wondering if anyone has worked with, or seen this issue, while integrating Netlify CMS into a Scully app.
    Sander Elias
    @SanderElias
    @hchings Yes, I'm fully on linux, and we are testing and using Scully in our own repo on github.
    hours for 300 routes sounds off. That might be a sign of too little memory assigned, or too little CPU (or both.
    @iiceman40 You can import 'scullyConfig' and have full access (If you are changing things on the fly there, any bugs are on you tho ;) )
    also, the second parameter of the routePlugins is the config for that particular route.
    @JoeyMckenzie If you have a reprodcuable scenario, I can take it up with our friends @ netlify
    Joey McKenzie
    @JoeyMckenzie
    @SanderElias created an issue for the team to take a look at when they get the chance. I have an irking suspicion this might be an issue with how I'm configuring Netlify CMS and Scully within an Nx monorepo containing multiple Scully apps. More than happy with you guys closing the issue if it's not withing the scope of Scully.
    Taylor Ackley
    @TaylorAckley
    Is is possible to give scully the /src/assets/scully-routes.json file and skip the other steps? We're using Angular Prerender with a simple routesfile and it worked great until we ran into long path issues. If there is a tutorial on it or another way I could give scully a list of complete paths I would be in your debt.
    Sander Elias
    @SanderElias
    @TaylorAckley We do have the 'extraroutes` config option. But I guess you might want to wait until the announcement on ng-conf.
    We currently don't have a way to entirely skip route-discovery, but you can tell the guess-parser to skip certain modules, there is a config option for that in the config file again.
    @JoeyMckenzie I'll take a look.
    Taylor Ackley
    @TaylorAckley
    thanks @SanderElias ... when I looked at the docs, the extraRoutes had params in them which made me think they had to be the raw paths.
    Sander Elias
    @SanderElias
    They can be both.
    Erin
    @hchings

    Hi all, when we manually look at the dist/static/ generated by Scully, index.htmls for pages with route parameters look correctly pre-renderede. However, when we deploy dist/static to prod, go to the same page w/ route params and click on "view source" in the browser, the source is the default root index.html rather than the correct one.

    This seem to be an nginx issue but I'm not sure which part to change. Appreciate if anyone can point me to the right direction / settings in nginx.

    Our current nginx.config (partial)

    http {
        include       mime.types;
        default_type  application/octet-stream;
    
        sendfile        on;
        #tcp_nopush     on;
    
        keepalive_timeout  65;
    
        gzip  on;
        gzip_vary on;
        gzip_min_length 10240;
        gzip_proxied expired no-cache no-store private auth;
        gzip_types text/plain text/css text/xml text/javascript application/x-javascript application/xml application/javascript;
        gzip_disable "MSIE [1-6]\.";
    
        server {
            listen           80;
    
            ssl                  on;
            ssl_certificate      /var/security/certificate.crt;
            ssl_certificate_key  /var/security/private.key;
    
            # server_name ${IP}:8080;
            server_name XXXX.com www.XXXX.com;
    
            #charset koi8-r;
    
            #access_log  logs/host.access.log  main;
              root /usr/share/nginx/html;          // <---  this is mounted to ./dist/satic/
              index index.html index.htm;
    
            location / {
                try_files $uri $uri/ /index.html;
    
            }
    
            # redirect server error pages to the static page /50x.html
            #
            error_page   500 502 503 504  /50x.html;
            location = /50x.html {
                root   html;
            }
    
        }
    
        include servers/*;
    }
    Lukas
    @elfunkhauser
    Hi guys, did anyone setup a Scully app on Heroku? I am experiencing some problems with puppeteer
    Sander Elias
    @SanderElias
    @hchings No expert on nging, but I suspect your location / { should be location * { (or the nging version of that)