> For the complete documentation index, see [llms.txt](https://docs.appstrategy.com/apprules-r-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstrategy.com/apprules-r-documentation/platform/self-hosting/software-installation/create-project.md).
# Creating a New Project Database
To create a new project database in appRules , select “Master Admin settings” from the file menu, log in with the Admin credentials and select the Create New Project Database option from the Admin Settings menu
In the “Create New Project Database” window below, enter a unique name for the new project database, and follow instructions to complete other fields. The database type and connection string are required.
Database Type:
Select the database type to use (EmbeddeDB, SQL Server, SQL Azure...). If you are unsure, you can utilize the default type of EmbeddedDB. When you select it, the connection string is automatically created for you (the database appdb file will be created in the C:\ProgramData\appStrategy\PortalData\Default\DbFiles directory).
Connection String:
Enter the connection string to be used for accessing the database. You
can optionally click on the button to configure the connection string.
The default user Admin (password: Admin) will be automatically created.
Click the OK button to create the project database or to save changes to the project database.
Optionnaly, Copy from another project dabase
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.appstrategy.com/apprules-r-documentation/platform/self-hosting/software-installation/create-project.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
