serverless / serverless/serverless

config file not found

Open
#11,031 1 comment 0 reactions 1 assignee View on GitHub

@ananthu7025 is already working on this.

Since May 4, 2022.

question
Dominant language
JavaScript
Stars
46.9k
Forks
5.7k
Avg merge
10h 7m
Merged PRs (30d)
57

Description

Are you certain it's a bug?
  • Yes, it looks like a bug
Is the issue caused by a plugin?
  • It is not a plugin issue
Are you using the latest version?
  • Yes, I'm using the latest version
Is there an existing issue for this?
  • I have searched existing issues, it hasn't been reported yet
Issue description

sh -ac " . ./.env.serverless.dev; serverless offline -c start while typing this command an error is comming config file start not found

Service configuration (serverless.yml) content
service: bidbuddy-v001

provider:
  name: aws
  runtime: nodejs6.10
  stage: ${file(./config/env.js):output.ENV}
  versionFunctions: false # optional, default is true
  region: ${file(./config/env.js):output.REGION}

functions: ${file(./config/functions.js)}

plugins:
  - serverless-webpack
  - serverless-dotenv-plugin
  - serverless-offline

package:
  individually: true

custom:
  dotenv:
    path: ./.env
Command name and used flags

N/A

Command output
N/A
Environment information
(node:3332) ExperimentalWarning: queueMicrotask() is experimental.
Serverless: DOTENV: Loading environment variables:
Serverless:      - ENV
Serverless:      - DOUBLECHECK
Serverless:      - DB_PASSWORD
Serverless:      - DB_DATABASE
Serverless:      - DB_HOST
Serverless:      - DB_USER
Serverless:      - REGION
Serverless:      - HASHING_SALT
Serverless:      - SALT_ROUNDS
Serverless:      - TOKEN_DURATION_SECONDS
Serverless:      - CSRF_COOKIE
Serverless:      - DOMAIN
Serverless:      - COOKIE_DOMAIN
Serverless:      - ORIGIN
Serverless:      - origin
Serverless:      - CLIENT_DOMAIN
Serverless:      - SU
Serverless:      - S3_BUCKET
Serverless:      - mail_user
Serverless:      - mail_password
Framework Core: 1.68.0
Plugin: 3.8.4
SDK: 2.3.2
Components: 2.34.9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.