Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Alexander Zaslonov
    @azaslonov
    Hi Keith, thank you let me check, I'll get back to you.
    Alexander Zaslonov
    @azaslonov
    Keith, looks like they just renamed "Basic" to "Email/Password", all the rest seems the same and working (for me at least).
    Can you tell which provider you're trying to setup? Have you added the user (looking at your error, it tries to do user signup)?
    Keith Lawrence
    @keithl8041
    Hey, thanks for the response. I figured that email/password is the same as Basic auth and I set it up and created a user. What's not clear to me is where I'm supposed to add the username/password to the config? I don't have a /src/config.json as mentioned in the docs and I can't find an obvious place to add the user credentials.
    Alexander Zaslonov
    @azaslonov

    You're right, there is a change in Firebase UI: there is no WEB SETUP option anymore, and hence, it is not clear how to put it into configuration. Sorry about that, we'll fix the docs.

    So, what you need to do is to put this into design.config.json to run the designer:

    {
        "firebase": {
            "apiKey": "< your API key >",
            "authDomain": "< your domain >.firebaseapp.com",
            "databaseURL": "https://< your database URL >.firebaseio.com",
            "projectId": "< your project ID >",
            "storageBucket": "< your storage bucket >.appspot.com",
            "databaseRootKey": "/",
            "storageBasePath": "/",
            "auth": {
                "basic": {
                    "email": "...",
                    "password": "..."
                }
            }
        },
        "environment": "design"
    }

    For publlishing, there are also some changes not mentioned in our docs (another thing to fix) - it is about service account private key:

    To generate a private key file for your service account:

    1. In the Firebase console, open Settings > Service Accounts.
    2. Click Generate New Private Key, then confirm by clicking Generate Key.
    3. Securely store the JSON file containing the key.
    4. Fill repsective fields in publish.config.json:
    {
        "firebase": {
            "apiKey": "< your API key >",
            "authDomain": "< your domain >.firebaseapp.com",
            "databaseURL": "https://< your database URL >.firebaseio.com",
            "projectId": "< your project ID >",
            "storageBucket": "< your storage bucket >.appspot.com",
            "auth": {
                "serviceAccount": {
                    "type": "service_account",
                    "project_id": "...",
                    "private_key_id": "...",
                    "private_key": "...",
                    "client_email": "...",
                    "client_id": "...",
                    "auth_uri": "https://accounts.google.com/o/oauth2/auth",
                    "token_uri": "https://oauth2.googleapis.com/token",
                    "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
                    "client_x509_cert_url": "..."
                }
            },
            "databaseRootKey": "/",
            "storageBasePath": "/"
        },
    ...
    Keith Lawrence
    @keithl8041
    thank you! I will give your instructions a go and report back. I appreciate the help.
    Alexander Zaslonov
    @azaslonov
    sure, hope that helps.
    Keith Lawrence
    @keithl8041
    Great - that's helped with the authentication to the server. Now I have some issues with permissions to database content, but I'll try sort that out myself by reading up on database rules. I think the default permissions have changed since the documentation was written. The one thing I don't understand is how to distinguish between anonymous users and "CMS editors" - I assume I should actually be using something like gmail authentication. Can you provide the auth: {} config for specifying which gmail users should be allowed to edit content?
    Keith Lawrence
    @keithl8041
    I guess my next question is, if I load it in incognito mode, why am I getting the edit interface if i don't have edit permissions?
    Alexander Zaslonov
    @azaslonov
    image.png
    the permissions get assigned on the Rules, and right, it is better to read Firebase docs to better understand it.
    you're getting editing interface because there is no logic to handle authentication/authorization. basically "demo" project is for demo purposes :) and the real usage hardly depends on the model of your application.
    here the firebase got chosen for demo puposes because it is fairly simple to start with and it has free tier which is great for developers to make PoC
    Keith Lawrence
    @keithl8041
    Makes sense - thanks. I'll play around with it some more. Thanks for the database rule example.
    Keith Lawrence
    @keithl8041
    I am getting nowhere with this. I can't work out how it's meant to work. The edit/design interface is cool and I can scope it down to just a single google user, but I can't figure out how to only show the published version to non-authenticated users and checking for auth before showing content doesn't make any sense anyway. So ideally I want a design interface available on a special URL that is only available to selected google users, and some kind of npm auto-publish script on save which writes the published files out to the CDN. Seems a weird setup though, I'm definitely missing something. Any thoughts?
    Mikhail Tuchkov
    @mtuchkov
    Would the managed version work better for you? Try https://dashboard.papersites.io
    It is in Early Access Program mode now, but is quite stable.
    Keith Lawrence
    @keithl8041
    Thanks - looks very interesting but I really want to use a custom domain so wouldn't mind trying to figure out a proper custom solution. Thanks for all your help.
    Alexander Zaslonov
    @azaslonov
    Sure, feel free to ping us anytime shall you need help.
    Peeomid
    @peeomid
    Hi, I'm considering to add paperbits into our app as page builder (using react) but a bit lost. Are there any document on integration? I couldn't find it on the site. Basically what I want to achieve, is to use Paperbits as page builder, and take the json output after editing, the rest will be handled by our app
    Alexander Zaslonov
    @azaslonov
    But there is no documentation yet.
    Peeomid
    @peeomid
    Right, thanks @azaslonov, I guess I'll need to figure it out myself for now then.
    Curious though, if I get the license, will there any support on integration, or it's just general setup and use support?
    Alexander Zaslonov
    @azaslonov
    Right, the primary purpose of the license is the support.
    Dedicated support if to be presice.
    fxhst329
    @fxhst329
    Hi
    I can't get any emails delivered to you, come back as not delivered and it keeps trying for couple days now.. any better way of contacting you?
    Mikhail Tuchkov
    @mtuchkov
    Hi, What email address have you tried?
    fxhst329
    @fxhst329
    support and operations
    image.png
    Alexander Zaslonov
    @azaslonov
    ok, we'll check what's going on, thanks for letting us know.
    do you have a question I believe?
    fxhst329
    @fxhst329
    yes, but let's exchange some contact
    Alexander Zaslonov
    @azaslonov
    ok, can you please email me at zaslonov.alexander@gmail.com
    fxhst329
    @fxhst329
    ok
    Alexander Zaslonov
    @azaslonov
    thanks
    RehanK
    @revdfdev
    Hello guys
    one question here
    can I add custom iframe / view into page builder
    if yes is there anything documentend about it
    ?
    Alexander Zaslonov
    @azaslonov
    Hi Rehan
    basically iframe could be a part of custom widget or represent a widget. There is an example widget "click-counter" in demo repository, it has react version as well.
    Kathy Church
    @kathychurch
    Is it possible to control access to parts of the generated sites to only authenticated users? I am thinking to have a login/signup button and once a user is authenticated, additional menu items become visible. Thanks!
    Alexander Zaslonov
    @azaslonov
    Hi Kathy, yes, there is a concept for that, you can even try it out on demo.paperbits.io.
    The only thing here, on demo site it is purely client side implementation, which means it only hides it with JS, so depending on your requirements, you may need to filter content on the fly on the backend