Build a User Management App with Angular
This tutorial demonstrates how to build a basic user management app. The app authenticates and identifies the user, stores their profile information in the database, and allows the user to log in, update their profile details, and upload a profile photo. The app uses:
- Supabase Database - a Postgres database for storing your user data and Row Level Security so data is protected and users can only access their own information.
- Supabase Auth - users log in through magic links sent to their email (without having to set up passwords).
- Supabase Storage - users can upload a profile photo.
note
If you get stuck while working through this guide, refer to the full example on GitHub.
Project setup#
Before we start building we're going to set up our Database and API. This is as simple as starting a new Project in Supabase and then creating a "schema" inside the database.
Create a project#
- Create a new project in the Supabase Dashboard.
- Enter your project details.
- Wait for the new database to launch.
Set up the database schema#
Now we are going to set up the database schema. We can use the "User Management Starter" quickstart in the SQL Editor, or you can just copy/paste the SQL from below and run it yourself.
- Go to the SQL Editor page in the Dashboard.
- Click User Management Starter.
- Click Run.
Get the API Keys#
Now that you've created some database tables, you are ready to insert data using the auto-generated API.
We just need to get the Project URL and anon
key from the API settings.
- Go to the API Settings page in the Dashboard.
- Find your Project
URL
,anon
, andservice_role
keys on this page.
Building the App#
Let's start building the Angular app from scratch.
Initialize an Angular app#
We can use the Angular CLI to initialize
an app called supabase-angular
:
_10npx ng new supabase-angular --routing false --style css_10cd supabase-angular
Then let's install the only additional dependency: supabase-js
_10npm install @supabase/supabase-js
And finally we want to save the environment variables in the environment.ts
file.
All we need are the API URL and the anon
key that you copied earlier.
These variables will be exposed on the browser, and that's completely fine since we have Row Level Security enabled on our Database.
Now that we have the API credentials in place, let's create a SupabaseService with ng g s supabase
to initialize the Supabase client and implement functions to communicate with the Supabase API.
Optionally, update src/styles.css to style the app.
Set up a Login component#
Let's set up an Angular component to manage logins and sign ups. We'll use Magic Links, so users can sign in with their email without using passwords.
Create an AuthComponent with ng g c auth
Angular CLI command.
Account page#
Users also need a way to edit their profile details and manage their accounts after signing in.
Create an AccountComponent with the ng g c account
Angular CLI command.
Launch!#
Now that we have all the components in place, let's update AppComponent:
app.module.ts
also needs to be modified to include the ReactiveFormsModule
from the @angular/forms
package.
Once that's done, run this in a terminal window:
_10npm run start
And then open the browser to localhost:4200 and you should see the completed app.
Bonus: Profile photos#
Every Supabase project is configured with Storage for managing large files like photos and videos.
Create an upload widget#
Let's create an avatar for the user so that they can upload a profile photo.
Create an AvatarComponent with ng g c avatar
Angular CLI command.
Add the new widget#
And then we can add the widget on top of the AccountComponent html template:
And add an updateAvatar
function along with an avatarUrl
getter to the AccountComponent typescript file:
Storage management#
If you upload additional profile photos, they'll accumulate
in the avatars
bucket because of their random names with only the latest being referenced
from public.profiles
and the older versions getting orphaned.
To automatically remove obsolete storage objects, extend the database
triggers. Note that it is not sufficient to delete the objects from the
storage.objects
table because that would orphan and leak the actual storage objects in
the S3 backend. Instead, invoke the storage API within Postgres via the http
extension.
Enable the http extension for the extensions
schema in the Dashboard.
Then, define the following SQL functions in the SQL Editor to delete
storage objects via the API:
_34create or replace function delete_storage_object(bucket text, object text, out status int, out content text)_34returns record_34language 'plpgsql'_34security definer_34as $$_34declare_34 project_url text := '<YOURPROJECTURL>';_34 service_role_key text := '<YOURSERVICEROLEKEY>'; -- full access needed_34 url text := project_url||'/storage/v1/object/'||bucket||'/'||object;_34begin_34 select_34 into status, content_34 result.status::int, result.content::text_34 FROM extensions.http((_34 'DELETE',_34 url,_34 ARRAY[extensions.http_header('authorization','Bearer '||service_role_key)],_34 NULL,_34 NULL)::extensions.http_request) as result;_34end;_34$$;_34_34create or replace function delete_avatar(avatar_url text, out status int, out content text)_34returns record_34language 'plpgsql'_34security definer_34as $$_34begin_34 select_34 into status, content_34 result.status, result.content_34 from public.delete_storage_object('avatars', avatar_url) as result;_34end;_34$$;
Next, add a trigger that removes any obsolete avatar whenever the profile is updated or deleted:
_29create or replace function delete_old_avatar()_29returns trigger_29language 'plpgsql'_29security definer_29as $$_29declare_29 status int;_29 content text;_29begin_29 if coalesce(old.avatar_url, '') <> ''_29 and (tg_op = 'DELETE' or (old.avatar_url <> new.avatar_url)) then_29 select_29 into status, content_29 result.status, result.content_29 from public.delete_avatar(old.avatar_url) as result;_29 if status <> 200 then_29 raise warning 'Could not delete avatar: % %', status, content;_29 end if;_29 end if;_29 if tg_op = 'DELETE' then_29 return old;_29 end if;_29 return new;_29end;_29$$;_29_29create trigger before_profile_changes_29 before update of avatar_url or delete on public.profiles_29 for each row execute function public.delete_old_avatar();
Finally, delete the public.profile
row before a user is deleted.
If this step is omitted, you won't be able to delete users without
first manually deleting their avatar image.
_14create or replace function delete_old_profile()_14returns trigger_14language 'plpgsql'_14security definer_14as $$_14begin_14 delete from public.profiles where id = old.id;_14 return old;_14end;_14$$;_14_14create trigger before_delete_user_14 before delete on auth.users_14 for each row execute function public.delete_old_profile();
At this stage you have a fully functional application!