Download the PHP package emilijus/bloom without Composer

On this page you can find all versions of the php package emilijus/bloom. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package bloom

Laravel 10 CRUD Generator Download here

Requirements

Laravel >= 10
PHP >= 8.2

Installation

  1. Run:

  2. Set the necessary permissions for the folders (storage, app, resources). Could be this (but not recommended):

  3. Run:

  4. Publish the vendor files:

  5. Connect to your database (inside the .env file) and make migration:

  6. Install the scaffolding of the program (it is recommended to use blade as the Breeze stack and PHPUnit option for testing since others were not tested just yet! ):

Commands

Install command:

The installation command: can be used for mainly three purposes.

The first one is the initial Admin Dashboard installation which is the first step in order to start using the generator.

The second purpose is to update the user table to add back the 'is_admin' flag if the database was refreshed, and the row got removed. This is done by running the command with a '--update-user-table flag': inside the terminal. This will add the 'is_admin' column back to the user table.

The third and final use is to create a new user with administrator privileges. This is done by running the command with a '--create-admin' flag: . After providing the required information, a new user will be created with administrator privileges.

Of course, the two flags can be used simultaneously to do both actions at the same time to save time.

Create command:

The create command is used to create a new CRUD module. It can be used by running the command: inside the terminal. This will start the process of creating a new CRUD module. However, the command requires some arguments to be passed in order to work properly. The arguments are as follows:

The creation command also has a few flags that can be used to customize the process of creating a CRUD module. The flags are as follows:

Delete command:

The delete command is used to remove a CRUD module. It can be used by running the command: inside the terminal. This will start the process of removing the models, views, controllers, and even migrations. The command requires only one argument: Name to be passed in order to work properly.

The deletion command also has a few flags that can be used to customize the process of deleting a CRUD module. The flags are as follows:

Supported Field Types

These fields are supported for command input:

Supported Validation Parameters

These validation parameters are supported for command input:

For images the mime types are set automatically (for now) they are: jpeg, png, jpg and gif. For images, it is recommended to use nullable (do not provide the required parameter when creating a CRUD with an image attribute). For example: .

CRUD creation via terminal example

Creating a CRUD via terminal is as simple as typing in a few sentences. Below you can find a step-by-step guide on how to create a full CRUD via the terminal commands. In this example, we are going to create a one-to-many relation between an Author and a Post. We will also use the --create-view flag to create a simple front-end view for our posts.

Here is what to do:

That is it! Now all you have to do is run the migration and everything will appear. To run the migration you can type: into the terminal.

Now, let us go to the pages page and create a new author and some posts. To do that just click on the View button and then select Create in the newly opened screen. After creating the author and a post we can proceed to the created view to see if the post appears on the frontend. Type in in your website URL or just use the Show button in the pages section to see the created posts. From here you can edit the views as you want to fit your needs.

CRUD creation via dashboard example

To create a CRUD from the dashboard all you have to do is go to the commands section, select the Create command, and follow the instructions there.

For our example, we would do these steps:

After creating a CRUD you can go to the pages section to migrate and see the created elements. To create, edit, or delete new elements for the created CRUD you can press the button on that page. If you also created the carcass of the front-end views you can press on the button in the pages section to see the created views.

CRUD deletion via terminal example

To delete a CRUD via terminal you need to provide the name for the command.

For example: . In addition, if we want to also remove the database tables for that CRUD we need to specify the drop tables flag: .

IMPORTANT! If you have an N:M relation and want to delete the tables from the database as well, you will have to also provide the pivot table name: .

CRUD deletion via dashboard example

To delete a CRUD all you need to do is select the CRUD from the dropdown in the Delete command.

In addition, if you want to delete the database tables as well, we would need to check the checkbox. IMPORTANT! If you have an N:M relation and want to delete the database tables, you will have to also provide the pivot table name.

For our example, we would do these steps:


All versions of bloom with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
laravel/breeze Version ^1.23
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package emilijus/bloom contains the following files

Loading the files please wait ....