Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Mar 31 08:37
    matthewdavidson removed as member
  • Mar 12 14:23
    matteofigus commented #1184
  • Mar 12 14:23
    matteofigus commented #1184
  • Mar 12 14:11
    dianatamas commented #1184
  • Mar 12 14:11
    dianatamas commented #1184
  • Mar 12 14:10
    dianatamas updated the wiki
  • Mar 12 14:10
    dianatamas updated the wiki
  • Mar 12 14:09
    dianatamas updated the wiki
  • Mar 12 14:09
    dianatamas updated the wiki
  • Mar 12 12:24

    matteofigus on master

    0.48.18 changelog (compare)

  • Mar 12 12:24

    matteofigus on master

    0.48.18 changelog (compare)

  • Mar 12 12:24

    matteofigus on v0.48.18

    (compare)

  • Mar 12 12:24

    matteofigus on v0.48.18

    (compare)

  • Mar 12 12:22
    matteofigus commented #1184
  • Mar 12 12:22
    matteofigus commented #1184
  • Mar 12 12:20

    matteofigus on master

    Add support for custom keepAliv… Merge pull request #1184 from d… (compare)

  • Mar 12 12:20

    matteofigus on master

    Add support for custom keepAliv… Merge pull request #1184 from d… (compare)

  • Mar 12 12:20
    matteofigus closed #1184
  • Mar 12 12:20
    matteofigus closed #1184
  • Mar 12 11:35
    dianatamas opened #1184
Matteo Figus
@matteofigus
Ok. Consider that you need some stuff to be public if you need client side rendering and for static assets..but if you do SSR only and you setup a CDN on top of s3 with the proper policies to go public, then you may be ok with full private.
But you may need to change some code in the registry to avoid saving with public ACL..which shouldn’t be too much effort
ALex
@aresobus_twitter

@matteofigus Hi! We use SSR only and I think I'll need to use you suggestion and override public part. So after in my server.js I should have something like this when I use storage adapter?

const oc = require('oc');
const s3 = require('oc-s3-storage-adapter');

let config = {
  baseUrl: 'my url', 
  port: 3000,
  refreshInterval: 600,
  pollingInterval: 5,
  templates: [require('oc-template-jade')],
  storage: {
    adapter: s3,
    options: {
      key: 'my key', 
      secret: 'my secret', 
      bucket: 'my bucket name',
      region: 'us-east-2',
      componentsDir: 'components',
      sslEnabled: false,
      s3ForcePathStyle: true,
      path - > ??
      debug: true,
      endpoint: 'http://localhost:8080'
    }    
  },
  env: { name: 'production' }
};

let registry = new oc.Registry(config);

registry.start(function(err, app){
  if(err) {
    console.log('Registry not started: ', err);
    process.exit(1);
  }
});

I was looking for some documentation for storage adapters, maybe you have some examples? The most part is self explanatory, but maybe I'll miss something accidentally or I need more configuration under 'options'...

Ken Crawford
@kmcrawford
ALex
@aresobus_twitter
@kmcrawford thank you !
ALex
@aresobus_twitter
@matteofigus @kmcrawford Hi guys, thank you so much for your help and suggestions, I made adjustments to the adapter and I'm able to work with fully private bucket & SSR. In order to do that we sacrifice components preview, but it is ok in our case.
The only thing that I want to optimize is a mechanism of getting components from the registry with private S3 bucket, now I have to send SECRET and KEY along with request(otherwise getting Access denied) to a registry trying to combine it with
client.renderComponents() but it makes rendering a little slower, so I hope I'm on the right track because I don't have any other option in my mind.
Have a great day !
Ken Crawford
@kmcrawford
:thumbsup:
Ken Crawford
@kmcrawford
@aresobus_twitter check out https://github.com/crunchyroll/evs-s3helper I haven’t used it but it should be able to proxy a private s3 bucket on an internal server
ALex
@aresobus_twitter

@kmcrawford wow thank you! I'm trying to do something like that in NodeJS and express.js router, so far can't get through access denied message.
My initial idea was to do following:

  1. get a pre-signed url's:
    const AWS = require('aws-sdk')
    const s3 = new AWS.S3()
    AWS.config.update({accessKeyId: 'id', secretAccessKey: 'key'})
    const myBucket = 'bucket-name'
    const signedUrlExpireSeconds = 60 * 5 <-- just a test
    const url = s3.getSignedUrl('getObject', {
     Bucket: myBucket,
     Key: "/",
     Expires: signedUrlExpireSeconds
    })
    console.log(url)
    And then pass it to the client = to have something like that:
const client = new Client({
    registries: {
      serverRendering: pre-signed url here <---

    },
  })

maybe I'm on the wrong track, will see

Matteo Figus
@matteofigus
I guess an easier way would be to use IAM if the consumer is running on aws too, so you don’t need to pass creds around which is risky and fragile. If the consumer is outside, you need creds. The only other strategy for rendering SSR without fetching view etc is asking the registry to do the render for you. When you make the rendering call, you can pass an accept header to ask for rendered result and the client should be able to handle the result. But obviously this is less optimal because you are overloading the registry with more compute and you are not caching the views on the clients impacting performance.
Try passing as header Accept: application/vnd.oc.rendered+json
ALex
@aresobus_twitter
@matteofigus I was looking at this conversation earlier:
opencomponents/oc#324
so I'm doing almost everything in the same way, except Accept header, will add that. The problem is that I can't go pass this step with fully private bucket to get a response:
POST https://oc-registry.com -H "Accept: application/vnd.oc.info+json"
{
  components: [{
    name: 'component1',
    version: '1.X.X'
  }, {
    name: 'component2',
    version: '~1.2.4'
  }]
}
but I think it's because I don't have enough experience with AWS and I'll find what is wrong
I need a credentials because consumer is outside ;(
Artëm Tsvetkov
@adeptex
hi all :wave: im getting into OC. i setup a local registry like this: oc dev ../components 3000 and put my test component in the components dir.
now if i open a new terminal and try oc registry add http://localhost:3000 i get this error:
not a valid oc registry
but i do see the request in the registry window:
GET / 200 0.514 ms - 160
is this a bug in the code or between keyboard and chair?
1 reply
Matteo Figus
@matteofigus
Hi Artem, the add command is used for setting a publish registry instance as target. When you run the oc dev you are running a local mock therefore that cannot be a publish target and the cli detects that.
1 reply
After you setup a registry you can add that url and then publish to it
No I’m afraid there isn’t. You can check the storage adapters where you can have various options outside of aws but all of them somehow need some storage. But the riak may be something you can investigate
ALex
@aresobus_twitter
@matteofigus @kmcrawford thank you for help earlier, I forget to mention that everything worked out and I found a way to make OC work with fully private bucket and now we have it running in PROD!
Ken Crawford
@kmcrawford
👍🏻
Matteo Figus
@matteofigus
Very nice!
Shinu Pushpan
@shinup
Hello I am trying to understand how Registry Rest API works . Tried to follow the documentation at https://github.com/opencomponents/oc/wiki/Registry . I am bit puzzled about how the registry will work if I want to host the registry in a AWS ECS (EC2) instance.
playforada97
@playforada97
Hi I am setting up OC project
oc init hello-world throwing error -bash: oc: command not found
https://github.com/opencomponents/oc/wiki I am following this instructions
ALex
@aresobus_twitter
@playforada97 run ```npm install -g oc```` it looks like you don't have framework installed
Matteo Figus
@matteofigus

Hello I am trying to understand how Registry Rest API works . Tried to follow the documentation at https://github.com/opencomponents/oc/wiki/Registry . I am bit puzzled about how the registry will work if I want to host the registry in a AWS ECS (EC2) instance.

@shinup after deploying the registry, you should have a base url you can use with the CLI. An easy way to get started with AWS is to use docker for the registry and use Elastic Beanstalk - an example of a container https://github.com/ciricihq/oc-docker

yugandhar-pathi
@yugandhar-pathi
@matteofigus i am new to open components .... after spending sometime i understand that it helps us to stitch micro front ends together ..is my understanding correct ?
Matteo Figus
@matteofigus
Yes
Ken Crawford
@kmcrawford
@matteofigus can I get a publish of storage-adapters?
Matteo Figus
@matteofigus
done @kmcrawford ;)
Anıl Aküzüm
@akuzumanl_twitter
How is the standard react web project configured with open component?
Ken Crawford
@kmcrawford
@yugandhar-pathi are you looking for something like this? https://github.com/opencomponents/react-oc
Matteo Figus
@matteofigus
Have a look at this one - it's the most updated one https://github.com/opencomponents/oc-template-react
marcabisamra
@marcabisamra
Hi 🙋🏻‍♂️are there any good video tutorials to get started with open components?
marcabisamra
@marcabisamra
We keep getting Registry not started: components_list_get with both the Getting started with Heroku and trying to get started locally
any way to get more information on whats going on? Followed this Heroku guide step by step and heroku outputting this
2021-03-15T20:23:45.713168+00:00 app[web.1]: > opencomponents-starter-kit@1.0.0 start /app 2021-03-15T20:23:45.713169+00:00 app[web.1]: > node server.js 2021-03-15T20:23:45.713169+00:00 app[web.1]: 2021-03-15T20:23:49.694652+00:00 app[web.1]: Registry not started: components_list_save 2021-03-15T20:23:49.842166+00:00 app[web.1]: npm ERR! code ELIFECYCLE 2021-03-15T20:23:49.844844+00:00 app[web.1]: npm ERR! errno 1 2021-03-15T20:23:49.887172+00:00 app[web.1]: npm ERR! opencomponents-starter-kit@1.0.0 start:node server.js`
Matteo Figus
@matteofigus
@marcabisamra I think that issue occurs if the application has no write/read permission to the S3 bucket. Can you check your bucket policy?
marcabisamra
@marcabisamra
That was it, thank you @matteofigus !
Matteo Figus
@matteofigus
no problem :thumbsup:
marcabisamra
@marcabisamra
When trying to use plugins (custom or from npm), I am constantly seeing an empty {} for context.plugins on the server even though i'm following the Wiki line by line on how to register them.. Is there a common mistake or something else I should know outside of the Register#plugins section of the wiki? @matteofigus 🙏
Diana Tamas
@dianatamas
Hi, we have been trying to migrate our registry to Kubernetes, but we're facing some issues, mainly when trying to get the list of existing components. We get the following error Error: EACCES: permission denied, mkdir '/srv/app/temp' at Object.mkdirSync (fs.js:921:3). I haven't been able to find where in the code mkdir is called (and why), does anyone have an idea? For more context, we are calling 127.0.0.1:8080/v2 (where /v2 is the prefix that we passed in the registry options, and 8080 the port in the options) in order to get the list of components
Matteo Figus
@matteofigus
@dianatamas when you publish a component you do a PUT to the registry, which is an express app using the multer module that uses a temp folder to save the package before uncompressing it and uploading objects to s3. I suspect the express registry is trying to create the temp folder at launch. You can override that setting in the config. Here is the default: https://github.com/opencomponents/oc/blob/master/src/resources/settings.js#L15
Maybe you can keep the settings as they are, but make sure the app can have write access to that folder
Matteo Figus
@matteofigus
@marcabisamra consider that you get the context.plugins in the registry when you run it with your storage. If you run the registry with the initialised components and you run a component using a valid plugin, and you don't see it there, the plugin may be invalid or not working correctly. But remember that when running locally in dev mode, plugins are not available so you need to mock them: https://github.com/opencomponents/oc/wiki/Cli#mock
Diana Tamas
@dianatamas
Thanks @matteofigus , I ended up changing the default setting and it worked!
Matteo Figus
@matteofigus

Thanks @matteofigus , I ended up changing the default setting and it worked!

:thumbsup: