Function Store
  • Home
  • Getting started
    • Introduction
    • Installing a function
    • Reconfiguring a function
    • Uninstalling a function
    • FAQs
  • Reference
    • Requirements
      • Assign Roles
        • User permissions
      • Link a Billing account to your project
      • Enable the APIs
    • Projects
      • How to add a project
      • How to set up a project
    • Functions
      • Benefits
      • Use cases
      • Authentication when installing
      • Runtime configuration
      • Deploying with a ZIP file
    • Policies
      • How to add a Policy
      • How to remove a Policy
    • Authentication
      • Users
      • Roles
      • Permissions
    • Secrets
      • Creating a Secret
      • Using a Secret
      • Changing the value for a Secret
      • Deactivating a Secret
  • developers
    • Overview
    • Getting Started
    • Set up
    • Workspaces
      • Create a workspace
      • Workspace boilerplate
      • Node engines
    • Writing Functions
      • Function Anatomy
      • Configuration file
      • Function Triggers
      • Environment Variables
        • Type "text"
        • Type "number"
        • Type "email"
        • Type "url"
        • Type "json"
        • Type "boolean"
        • Type "select"
        • Type "multiselect"
        • Type "firestoreDocumentPath"
        • Type "firestoreCollectionPath"
        • Type "color"
      • Documentation
    • Push/Update your functions in the cloud
    • Continuous Integration
    • Publish functions in the Marketplace
    • Emulators
      • Initialize emulators in your workspace
      • Environment variables
      • Starting emulators
      • Testing your functions in the emulator
      • Importing existing data into local emulators
        • Exporting data from Cloud Firestore to local emulator
        • Exporting user accounts from Firebase to local emulator
    • Visual Studio Code Extension
      • Installing the extension
      • Extension UI
      • Functions list
      • Creating and editing functions
      • Emulators
      • Extension settings
      • Troubleshooting
        • "Command not found" error when executing a command
  • Billing
    • Understanding Billing
  • Security
    • Security
  • Resources
    • Events and Triggers
    • Best Practices
      • How to log events in functions?
    • Document your Functions
    • Editorial guidelines
    • Our Processes
      • Use Cases Analysis
  • Use cases
    • Custom Stripe Checkout
Powered by GitBook
On this page
  • What you need to know
  • Function Store code base
  • Requirements
  • What's next

Was this helpful?

  1. Getting started

Introduction

Get up and running with Function Store marketplace platform in a few steps.

PreviousHomeNextInstalling a function

Last updated 3 years ago

Was this helpful?

What you need to know

Function Store code base

Function Store is built with JavaScript and is a Serverless Cloud Functions marketplace. You can deploy these functions in your Firebase and Google Cloud Platform (GCP) projects without your codebase getting mired in complexity. If at any point you are looking for answers that you can't find here, try looking at Firebase and GCP documentation.

Requirements

Before you can start using Function Store, make sure that you have an active Google account. If you don't have one yet, please create it here. Then you need to create a Firebase or GCP project and log in to Function Store.

Note that when you log in, a service account is automatically created for you. This will help us manage things for you.

Roles

Once in the app, you have to add that project to the Project list by assigning the following roles to a service account:

  • Cloud Function Admin

  • Firebase Authentication Admin

  • Secret Manager Admin

  • Service Account User

  • Service Usage Admin

These roles contain a set of permissions that allows you to perform specific actions on GCP resources. To know more about permissions, go to:

Billing account

You must link your project to a Billing account on GCP. This is a GCP requirement and is used to define who pays for a given set of Google Cloud resources and Google Maps Platform APIs. To know more about permissions, go to:

Enable APIs

Your project must also have these APIs enabled in GCP: the Cloud Functions API, the Cloud Build API, and the Secret Manager API. The first one manages lightweight user-provided functions executed in response to events, and the second one stores sensitive data such as API keys, passwords, and certificates.

To know more about APIs and how to enable them, go to:

What's next

Let's install a function!

User permissions
Link a Billing account to your project
Enable the APIs
Installing a function