Mongo DB

Hey guys, I know that the first way to get the platform started is by using “docker-compose up” however what I have been trying to do is start up the individual code bases.

Now after a lot of attempts, I realized that when you start the whole stack through docker, it creates a local Mongo instance on port 27000 which is otherwise not accessible.

So if I want to use Mongo Atlas or say run the platform without docker (by individually running npm serve or np run devstart, how would I do that?

Cheers!

[AmandaDLyon]

@smaharj1 I feel like this issue needs to be separated from this discussion thread as the topics aren’t the same. Please refer to and provide a solution at #132.

Thanks buddy!

[AmandaDLyon]

@smaharj1 I finally got S3 to work. Below is the Bucket Policy I set:

{
    "Version": "2012-10-17",
    "Id": "Policy1594102782490",
    "Statement": [
        {
            "Sid": "Stmt15941012824",
            "Effect": "Allow",
            "Principal": "*",
            "Action": "s3:*",
            "Resource": "arn:aws:s3:::name-of-bucket"
        }
    ]
}

and this is the CORS config that I used:

<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
    <AllowedOrigin>http://localhost:5202</AllowedOrigin>
    <AllowedMethod>PUT</AllowedMethod>
    <AllowedMethod>POST</AllowedMethod>
    <AllowedMethod>DELETE</AllowedMethod>
    <MaxAgeSeconds>3000</MaxAgeSeconds>
    <ExposeHeader>x-amz-server-side-encryption</ExposeHeader>
    <ExposeHeader>x-amz-request-id</ExposeHeader>
    <ExposeHeader>x-amz-id-2</ExposeHeader>
    <AllowedHeader>*</AllowedHeader>
</CORSRule>
</CORSConfiguration>